This section explains the 62XXX message series.
[Description]
key must be specified.
[Corrective Action]
If this message is output during the following operations:
Check the content of the XML file specified when operating the server, and correct the elements and values specified in key.
Creating an L-Server
For details on the elements and the values, refer to "2.3 L-Servers".
When creating another L-Server using detailed L-Server information, which is output using the rcxadm lserver show command, refer to "Creating another L-Server using detailed L-Server information" of "2.3.1 Definition Information for Physical L-Servers (XML)" or "2.3.2 Definition Information for Virtual L-Servers (XML)".
Importing an L-Server template
For details on the elements and the values, refer to "2.2 L-Server Template".
Registration of iSCSI boot information
For details on the elements and the values, refer to "2.4.2 iSCSI Boot Information".
Registering or changing disk resources for a VM guest
Take corrective action based on the content of key.
"Storage"
It is necessary to define the Storage element.
"Pool"
It is necessary to define the Pool element.
"Pool.name"
It is necessary to define the name attribute for the Pool element.
"VmHosts"
It is necessary to define a VmHosts element.
"VmHost"
It is necessary to define a VmHost element.
"VmHost.ip"
It is necessary to define the ip attribute for the VmHost element.
"VmHost(ip=IP address of the VM host defined in XML).Disks"
It is necessary to define a Disks element in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
"VmHost(ip=IP address of the VM host defined in XML).Disks.Disk"
It is necessary to define a Disk element in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
"VmHost(ip=IP address of the VM host defined in XML).Disks.Disk.name"
It is necessary to define the name attribute in the Disk element in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
"VmHost(ip=IP address of the VM host defined in XML).Disks.Disk(name=Disk resource name defined in the XML).size"
It is necessary to define the size attribute for the Disk tag to which disk resource name defined in XML is specified for name, in the VmHost element to which an IP address of the VM host defined in the 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"
It is necessary to define the path attribute for the Disk element to which disk resource name defined in XML is specified for name, in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
"Disk(name=disk resource name specified in -name of rcxadm disk modify)"
It is necessary to define the Disk element to which the disk resource name specified in -name of rcxadm disk modify is specified for the name attribute in the XML.
For details on the elements and the values, refer to "2.4.1 Disk Resources [KVM]".
Importing network configuration information or creating network devices
For details on the elements and the values, refer to "2.6.1 Creation".
If this message is output when creating or modifying a virtual L-Server
Review the settings in the dialog, and perform the operation again.
If this message is output when starting a virtual L-Server
Check the values in the L-Server definition settings, and perform the operation again.
Take corrective action based on the content of key.
"OSSetting.AdminPassword"
Specify the "Administrator password" on the [OS] tab.
"OSSetting.DNSSearchPaths.DNSSearchPath"
Specify the "DNS Search Path" on the [OS] tab.
For the values, refer to "Chapter 10 Creating L-Servers" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
"port group"
Check that there are no incomplete descriptions for the virtual bridge or VLAN ID in the virtual network definition file.
If this message is output when importing DR
Check the content of the XML file specified when operating the server, and correct the elements and values specified in key.
If this message appears when linking a configured virtual machine with an L-Server and key is "CPU.NumOfCPU"
Confirm that the VM host is managed by the VM management software and then perform the operation again.
[Description]
template is being used by the L-Server output in obj.
If there are three or more L-Server names output in obj, only two are displayed, followed by "...".
[Corrective Action]
If you do not want to use the template template used when creating the L-Server again, perform the following operations:
Add the -force option to the command, and perform the operation again
Delete the L-Server template from the ROR console
[Description]
An error occurred during the control of storage management software, so registration of the storage management software obj failed.
[Corrective Action]
Take corrective action based on the content of detail.
"version unmatch. [version_of_the_storage_management_software]"
There is an error in the version_of_the_storage_management_software. Use a supported version.
"service is not run."
The storage management software is not operating. Start the storage management software.
"invalid storage management software name"
There is an error in the name specified for the -soft_name option. Specify the correct name.
"one or more option is short"
A required option has not been specified. Specify the required option.
"one or more option is unnecessary"
An unnecessary option has been specified. Do not specify unnecessary options.
"storagemgr is already registered"
The specified storage management software has already been registered. Storage management software that is already registered cannot be registered.
"ip address:invalid format"
There is an error in the specified IP address. Specify the correct IP address.
"port:invalid format"
There is an error in the specified port number. Specify the port number using a decimal number.
"port: out of range"
There is an error in the specified port number. Specify the port number in the range of 0 to 65535.
"command failed."
Storage management software may not be able to be used. Check whether storage management software is available.
In the following cases, storage management software is unavailable. Check that the preparations have been completed, referring to "4.3.1.1 Storage Environment Preparation" in the "Setup Guide CE".
When the IP address for access to the storage management software specified with the -ip option is incorrect
When descriptions in the storage connection definition file are incorrect
When a security file has not been created
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
An error occurred during control of storage management software, so changes to the configuration of the storage management software obj failed.
[Corrective Action]
Take corrective action based on the content of detail.
"storagemgr is registered as VM management software"
This command cannot be used to make configuration changes, as storage management software has been registered as VM management software. For how to modify the settings for VM management software, refer to "3.8 Changing VM Management Software Settings" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
"one or more option is unnecessary"
An unnecessary option has been specified. Do not specify unnecessary options.
"ip address:invalid format"
There is an error in the specified IP address. Specify the correct IP address.
"port:invalid format"
There is an error in the specified port number. Specify the port number using a decimal number.
"port: out of range"
There is an error in the specified port number. Specify the port number in the range of 0 to 65535.
"storagemgr is registered as iSCSI controller"
This command cannot change resources, as the disk used for iSCSI boot has been registered.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
An error occurred in the control of the storage management software, so deletion of the storage management software obj failed.
[Corrective Action]
Take corrective action based on the content of detail.
"storagemgr is registered as VM management software"
This command cannot be used for deletion as the storage management software has been registered as VM management software. For how to delete VM management software, refer to "5.6 Deleting VM Management Software" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
"storagemgr is registered as iSCSI controller"
This command cannot delete resources, as the disk used for iSCSI boot has been registered.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in detail, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
The L-Server cannot be deleted because the VM host vm_host on the L-Server server_name is registered with the VM pool pool.
[Corrective Action]
When deleting the L-Server, delete the registration of the VM host vm_host from the VM pool pool, and then perform the operation again.
[Description]
It is necessary to specify the "-allow deldisk" option when executing the command, because this operation may delete the disk contents.
The name of the L-Server or the disk is displayed for resource.
[Corrective Action]
Specify the "-allow deldisk" option for the command, and perform the operation again.
When backing up the disk contents of L-Server, perform this corrective action and then perform the operation again.
[Description]
The resource resource_name cannot be selected.
In resource_name, the resource name is displayed.
In detail, the following detailed information is displayed:
"physical_server is user not privileged"
Cannot be selected because the physical server does not have access privileges.
"physical_server is not selectable status"
Cannot be selected because the status of the physical server is error.
"physical_server is specified spare server"
Cannot be selected because the specified physical server has been configured as a spare server in the server resource tree.
"physical_server is not preserved by lserver lserver"
Cannot be selected because the physical server is being used as another L-Server.
"physical_server is already set up"
Cannot be selected because a server profile has been allocated to the physical server.
"invalid model name"
Cannot be selected because there is an error in the model name of the physical server.
"physical_server is incompatible model model and model"
Cannot be selected because the model of the physical server is incompatible.
"physical_server can not get spec cpu or memory"
Cannot be selected because the information about the CPU or memory of the physical server cannot be obtained.
"physical_server spec is low"
Cannot be selected because the information about the CPU, memory, NIC, and FC of the physical server does not meet the defined conditions.
"physical_server is not blade. fc-connection pattern is valid only blade."
"FC connection pattern" is valid with blades only.
"admin LAN pair is not the same between index and index"
Cannot be selected because the combination of the admin LAN pair of the physical server is different from the definitions for physical L-Server creation.
"physical_server is search locked"
Failed because multiple operations of physical L-Server creation were performed at the same time.
"physical_server is search locked"
Cannot be selected because the physical server is used for multiple processes.
"physical_server is preserved. but lserver is repurpose false"
Cannot be selected because the physical server has been released while resource release was not specified when creating the L-Server.
"server type is not the same between"
Cannot be selected because the server type (blade server or rack mount server) of the physical server is different from the definition.
"Virtual I/O type is not the same between"
Cannot be selected because the virtualization method of the physical server is different.
"admin LAN position is not the same between index and index"
Cannot be selected because the position of the admin LAN of the physical server is different from the definitions for the physical L-Server.
[Corrective Action]
Take the following corrective action based on the content of detail.
"physical_server is user not privileged"
Grant the physical server access privileges and perform the operation again.
"physical_server is not selectable status. state status"
Check the status of the physical server, and then perform the operation again.
"physical_server is specified spare server"
Cancel the spare server settings, and then perform the operation again.
"physical_server is not preserved by lserver lserver"
Change the physical server status to unused, and then perform the operation again.
"physical_server is already set up"
Check the status of the physical server, and then perform the operation again.
"invalid model name"
Review the model name that was specified during creation of the physical L-Server, then perform the operation again.
"physical_server is incompatible model model and model"
Check the model compatibility of the physical server, and then perform the operation again.
For details, refer to "Table 14.1 List of Items Specified in Definition Files for Checking Spare Server Models and Configurations" in "14.1.1 L-Server High Availability" of the "Operation Guide CE".
"physical_server can not get spec cpu or memory"
Confirm that the CPU and memory information of the physical server has been configured, and then perform the operation again.
"physical_server spec is low"
Review the CPU, memory, NIC, and FC (*1) information that was specified during creation of the physical L-Server, and then perform the operation again.
*1 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.
"physical_server is not blade. fc-connection pattern is valid only blade."
"FC connection pattern" is valid with blades only.
"admin LAN pair is not the same between"
Confirm that the admin LAN information of the physical L-Server and physical server has been configured, and then perform the operation again.
"physical_server is search locked"
Multiple operations of physical L-Server creation were performed at the same time. Perform the operation again.
"physical_server is search locked"
Check if the physical server is being used for multiple processes, and then perform the operation again.
"physical_server is preserved. but lserver is repurpose false"
Specify resource release when creating the physical L-Server, then perform the operation again.
"server type is not the same between"
Confirm the server type (blade server or rack mount server) used when creating the physical L-Server and then perform the operation again.
"Virtual I/O type is not the same between"
Check the virtualization method setting for the physical server, and then perform the operation again.
"admin LAN position is not the same between index and index"
Check the physical L-Server definition and admin LAN position between physical servers, and then perform the operation again.
[Description]
An address outside of the specifiable address scope was specified when performing the following operations:
Creating an L-Server
Changing Network Configuration
Registering Managed Servers
Changing Managed Servers
In address, the specified address is displayed.
In start, the start value of the subnet address or start value of the address set resource is displayed.
In end, the end value of the subnet address or end value of the address set resource is displayed.
In resource name, the name of either the network resource or address set resource is displayed.
Start value and end value are included in the specifiable scope.
[Corrective Action]
Specify an address within the specifiable scope, and perform the operation again.
[Description]
An error occurred during control of storage management software.
In obj, the resource name of the storage management software is displayed.
For ipaddress, the IP address of the target resource is displayed.
In %1, the internal function name is displayed.
In %2, the internal code information is displayed.
In %3, the internal detail information is displayed.
[Corrective Action]
When using NetApp as storage management software
Take corrective action based on the content of %2.
If %2 is "13062"
Since the specified disk size is larger than the available space, creation of a volume on the storage unit failed.
Perform the operation again after modifying the disk size.
If %2 is "13115"
Since the specified disk size is less than 20MB, creation of a volume on the storage unit failed.
Perform the operation again after modifying the disk size.
When using PRIMECLUSTER GDS as storage management software
When %1 is /usr/sbin/sdxvolume, and %3 contains "no enough space"
Since the specified disk size is larger than the available space, creation of a volume on the storage unit failed.
When "Permission denied" or "not privileged" is included in %3
The user specified when registering the storage management software does not have sufficient privileges to execute the command.
Change the user name for the storage management software.
For details, refer to "1.7.1 rcxadm storagemgr".
When %1 is /usr/sbin/sdxvolume, and %3 contains "class closed down", or when %1 is /bin/dd, and %3 contains "No such device or address"
A failure may occur on the disk used as virtual storage.
Refer to the PRIMECLUSTER GDS manual.
When %1 is /usr/sbin/sdxvolume, and %3 contains "related to proxy volume"
In the settings of PRIMECLUSTER GDS, a proxy volume is related to a disk.
After deleting the relationship using PRIMECLUSTER GDS, perform the operation again.
When a character string beginning with "/usr/sbin/sdx" is displayed in %1
An error occurred while executing a PRIMECLUSTER GDS command.
Refer to the PRIMECLUSTER GDS manual.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in internal code information, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
An error occurred during control of storage management software.
In obj, the resource name of the storage management software is displayed.
In %1, the internal function name is displayed.
In %2, the message of the storage management software is displayed.
[Corrective Action]
When the target storage is ETERNUS
When %2 is "ERROR:ssmgr3419:The specified alias name has already been registered."
Creation or startup of the L-Server failed because the alias name of the affinity group has already been defined when ETERNUS storage was created.
For corrective actions, refer to "When an L-Server is Created or Started, "Message number 62511" is Displayed, then Creation or Startup of the L-Server Fails.".
When %2 is "ERROR:ssmgr3422:As for specified volume Volume_number, the LUN mapping is done."
Connecting a disk resource to an L-Server has failed because the Volume corresponding to the disk resource had already been mapped.
For corrective actions, refer to "When a Disk Resource is Connected to an L-Server, "Message number 62511" is Displayed and Connection Fails.".
When any other message is displayed
Performing corrective actions referring to the ETERNUS SF Storage Cruiser manual, and then perform the operation again
When the target storage is EMC CLARiiON, EMC Symmetrix DMX or EMC Symmetrix VMAX
When %2 is "lunmask doesn't set it."
A disk resource connected to an L-Server has been released from storage management software.
Detach the disk resource from the L-Server, and then perform the operation again.
When any other message is displayed
Perform the operation again after performing corrective actions referring to "3.2 Messages Beginning with swsag or ssmgr".
When using any other storage
Perform operations again after performing corrective actions, referring to the storage management software manual.
[Description]
There is an error in the file format specified for filename.
The details of the error are displayed for %1.
[Corrective Action]
When executing the rcxstorage command:
Take corrective action based on the content of %1.
"specified target volume not found in ROR (line:n)"
The disk resource corresponding to the target volume for replication specified on line n of the replication definition file specified for filename has not been detected and displayed in the resource tree. Check that the target volume for replication is correctly specified, and then execute the command again.
"number of column must be 4 (line:n)"
There is an error with the number of columns in line n of the replication definition file that is specified for filename. Check that the number of columns is 4, and then execute the command again.
"empty file"
There is no content in the replication definition file specified for filename. Check that the content of the replication definition file is correct, and then execute the command again.
"field missing a value (line:n)"
A column with no value set exists in line n of the replication definition file specified for filename. Set the value for the column, and then execute the command again.
"definition conflict with line m (line:n)"
The definition in line n of the replication definition file specified for filename is found again in line m. Correct the volume, and execute the command again.
"specified target volume not found in ROR (line:n)"
The disk resource corresponding to the target RAID group or TPP for replication specified on line n of the mirroring definition file specified for filename has not been detected and displayed in the resource tree. Check that the target RAID group or TPP for replication is correctly specified, and then execute the command again.
[Description]
Registration of the resource resource_name has failed.
In resource_name, the name of the virtual storage resource or the disk resource is displayed. When multiple resources are operated using one operation, only the first resource name an inconsistency was detected for is displayed.
In resource_type, "vstorage" or "disk" is displayed.
When detail is "attribute of thick/thin provisioning conflicts with target"
Failed due to inconsistencies in the attribute combination of thin provisioning or thick provisioning with the destination storage pool for registration or movement.
In target, the name of the storage pool is displayed.
[Corrective Action]
Check the content displayed in detail, and then perform the operation again.
When detail is "attribute of thick/thin provisioning conflicts with target"
Make sure that there are no inconsistencies in thin or thick provisioning attributes between resource_name and target, and then perform the operation again.
If this message is output when detaching a disk from a virtual L-Server, either move the virtual storage in which that disk exists to an appropriate thin/thick pool, or create an appropriate thin/thick disk and copy the data to that disk, and then perform the operation again.
[Description]
No available VM host was found.
The error may be the result of one of the following:
There is no object that meets the conditions
Creation of an L-Server from the ROR console, specifying values in the definition file. The values are larger than the actual number of CPUs and CPU clock speed of a server for which server management software is not used
In environments where Hyper-V VM hosts without Windows Server 2008 R2 Service Pack 1 (SP1) or SCVMM that has not been upgraded to System Center Virtual Machine Manager 2008 R2 Service Pack 1 (SP1) or later are being used, one of the following operations was performed:
Creation of an L-Server for which dynamic memory is enabled
Enabling of dynamic memory using L-Server specification changes
In environments where an SCVMM that has not been upgraded to Microsoft(R) System Center 2012 Virtual Machine Manager or later is being used, the following operation was performed:
Creation of an L-Server specifying a disk that was allocated from a virtual storage and saved
[Corrective Action]
Take corrective action based on the content of detail.
"one of power status, monitoring status, or maintenance mode is invalid"
Perform the operation again after checking whether a VM host in the following state exists:
Power is ON
Monitoring status is normal
Maintenance mode is not set
Maintenance mode has not been set for the server virtualization software
"no other available VM host found"
When performing migration, if this message is output, take the following corrective action according to the values specified during migration:
When specifying "Automatic Selection" for the destination VM host, or when executing the rcxadm lserver migrate command without specifying the -to option)
The resources used by the L-Server do not contain a VM host that satisfies the conditions described in "one of power status, monitoring status, or maintenance mode is invalid", except the one to migrate.
Specify the destination VM host, and then perform the operation again.
For how to confirm the resources to use, refer to "11.7 Migration of VM Hosts between Servers" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When specifying "VM host" for the destination VM host, or when executing the rcxadm lserver migrate command specifying the -to option)
The specified VM host does not satisfy the conditions described in "one of power status, monitoring status, or maintenance mode is invalid". Specify another VM host, and then perform the operation again.
"not enough CPU or memory available"
There is a chance that there are not enough available resources for the CPU or memory of a VM pool. Check the available resources for the CPU and memory of the VM pool.
Perform the operation again after performing the following corrective actions:
If there is insufficient CPU performance or memory resources of the VM pool
Add a VM host to the VM pool.
If there is no VM host in the VM pool that meets CPU performance or the number of CPUs specified for an L-Server or an L-Server template
Change the CPU performance or the number of CPUs specified for an L-Server or an L-Server template, or add a VM host meeting the necessary performance to the VM pool.
"there is a VM host with sufficient reservation capacity, but not enough CPU or memory"
There is a possibility that there is a VM host with sufficient reservation capacity for failover in the VM pool, and there are not enough available CPU or memory resources in the VM pool. Check the cluster configuration of the server virtualization software, correct the reservation capacity, and then perform the operation again.
If the problem is still not resolved after performing the corrective actions above, perform the following corrective actions:
If there is insufficient CPU performance or memory resources of the VM pool
Add a VM host to the VM pool.
If there is no VM host in the VM pool that meets CPU performance or the number of CPUs specified for an L-Server or an L-Server template
Change the CPU performance or the number of CPUs specified for an L-Server or an L-Server template, or add a VM host meeting the necessary performance to the VM pool.
"no sharable datastore found"
Perform the operation again after checking whether a VM host sharing a datastore exists.
If this message is displayed when performing migration, check whether the datastore is shared between the VM host where the L-Server is deployed and the "VM host" set for the L-Server using VM management software. If the datastore is not shared, specify a VM host that shares the datastore with the destination VM host, and then perform the operation again.
When migrating between VM hosts that do not share a datastore, perform the operation using VM management software.
For how to confirm the VM host to use, refer to "11.7 Migration of VM Hosts between Servers" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If this message is output when creating or starting a virtual L-Server that has disk resources that were created (and saved) from virtual storage, check all such disk resources connected to the L-Server and ensure that a VM host that can access the datastore which generated such disk resources exists, and then perform the operation again.
"no valid HA configuration of the server virtualization software found"
Check and correct the following from the management window of the server virtualization software, and perform the operation again.
That there are two or more VM hosts in the same cluster on the server virtualization software
That the HA function is enabled in the cluster configuration of the VM hosts
"no accessible VM host or VM pool found"
Check the following and perform the operation again.
That there is an accessible VM pool
That there is a VM host in the VM pool
When an L-Server has been created without configuring overcommit, depending on the VM host selection status, confirm the following:
When "Automatic Selection" is selected
If a VM pool for which overcommit is not configured exists in the accessible area, and if a VM host exists under the VM pool
When "VM Pool" is selected
If overcommit is not configured in the specified VM pool, and if a VM host exists under the VM pool
For details on overcommit, refer to the "Overcommit" section of the server virtualization software to use in the "Appendix E Design and Configuration For Creating Virtual L-Servers" in the "Setup Guide CE".
[Hyper-V]
Check if Windows Server 2008 R2 Service Pack 1(SP1) has been applied to the VM hosts and if SCVMM has been upgraded to System Center Virtual Machine Manager 2008 R2 Service Pack 1 (SP1) or later. If not, apply the appropriate Service Pack and then perform the operation again. When not applying Service Pack, disable dynamic memory and the priority of memory allocation, and perform the operation again.
"no accessible VM pool for over commit found"
Check the following and perform the operation again.
That there is a VM pool for overcommit and that there is a VM host under that VM pool
That both VM pools (the one that is set for overcommit and the one that is not) are inside the access scope
For details on overcommit, refer to the "Overcommit" section of the server virtualization software to use in the "Appendix E Design and Configuration For Creating Virtual L-Servers" in the "Setup Guide CE".
"combination of image and VM host combination is incorrect"
A template corresponding to the cloning image to deploy and the VM host to which the cloning image is deployed must belong to the Oracle VM server pool.
On Oracle VM Manager, perform configuration so the VM host exists in the same Oracle VM server pool as the template corresponding to the cloning image to deploy.
Also, register the VM host in a VM pool included in the access scope, 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.
For how to check the VM host status and free space, refer to "12.4 Viewing a Resource Pool" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
"product version of VM management software"
Check if the SCVMM being used has been upgraded to Microsoft(R) System Center 2012 Virtual Machine Manager or later. If not, upgrade the SCVMM and then perform the operation again.
[Description]
The specified VM host cannot be used.
The error may be the result of one of the following:
The specified VM host does not satisfy the conditions for the given operation
Creation of an L-Server from the ROR console, specifying values in the definition file. The values are larger than the actual number of CPUs and CPU clock speed of a server for which server management software is not used
In environments where Hyper-V VM hosts without Windows Server 2008 R2 Service Pack 1 (SP1) or SCVMM that has not been upgraded to System Center Virtual Machine Manager 2008 R2 Service Pack 1 (SP1) or later are being used, one of the following operations was performed:
Creation of an L-Server for which dynamic memory is enabled
Enabling of dynamic memory using L-Server specification changes
[Corrective Action]
Check the content displayed in detail, and take corrective actions described in "Message number 62514".
[Description]
The port combination for the storage unit at storage_unit_ipaddr is not defined in the port combination definition file for SAN storage "storage_portset.rcxprop".
In storage_unit_ipaddr, one of the following is displayed:
For ETERNUS Storage
The IP address of the admin LAN port of ETERNUS storage is displayed.
For EMC CLARiiON Storage
The IP address of the SP of EMC CLARiiON storage is displayed.
For EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage
The Symmetrix ID of EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage is displayed.
In pattern, the following is displayed:
SAN storage port combination definition file
"storage_portset. rcxprop" is displayed.
FC connection pattern file
"FC connection pattern file name.rcxprop" is displayed.
[Corrective Action]
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should define the port combination for the storage unit at storage_unit_ipaddr, referring to "6.1.1 Creating Definition Files for Combining Ports for SAN Storage" or "Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE".
[Description]
In the port combination definition file for SAN storage, "storage_portset.rcxprop", an unavailable port is defined for the port combination for the storage unit at storage_unit_ipaddr.
In port, the unavailable port that is defined in the port combination definition file for SAN storage, "storage_portset.rcxprop", is displayed.
In storage_unit_ipaddr, one of the following is displayed:
For ETERNUS Storage
The IP address of the admin LAN port of ETERNUS storage is displayed.
For EMC CLARiiON Storage
The IP address of the SP of EMC CLARiiON storage is displayed.
For EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage
The Symmetrix ID of EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage is displayed.
In pattern, the following is displayed:
SAN storage port combination definition file
"storage_portset. rcxprop" is displayed.
FC connection pattern file
"FC connection pattern file name.rcxprop" is displayed.
[Corrective Action]
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should review the port combination for the storage unit at storage_unit_ipaddr, referring to "6.1.1 Creating Definition Files for Combining Ports for SAN Storage" or "Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE".
[Description]
Duplicate port combinations are defined for the storage unit at storage_unit_ipaddr in the port combination definition file for SAN storage "storage_portset.rcxprop".
In port, the duplicate port that is defined in the port combination definition file for SAN storage, "storage_portset.rcxprop", is displayed.
In storage_unit_ipaddr, one of the following is displayed:
For ETERNUS Storage
The IP address of the admin LAN port of ETERNUS storage is displayed.
For EMC CLARiiON Storage
The IP address of the SP of EMC CLARiiON storage is displayed.
For EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage
The Symmetrix ID of EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage is displayed.
In pattern, the following is displayed:
SAN storage port combination definition file
"storage_portset. rcxprop" is displayed.
FC connection pattern file
"FC connection pattern file name.rcxprop" is displayed.
[Corrective Action]
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should review the port combination for the storage unit at storage_unit_ipaddr, referring to "6.1.1 Creating Definition Files for Combining Ports for SAN Storage" or "Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE".
[Description]
The port combination for the storage unit at storage_unit_ipaddr defined in the port combination definition file for SAN storage, "storage_portset.rcxprop", is not defined using a port pair.
In storage_unit_ipaddr, one of the following is displayed:
For ETERNUS Storage
The IP address of the admin LAN port of ETERNUS storage is displayed.
For EMC CLARiiON Storage
The IP address of the SP of EMC CLARiiON storage is displayed.
For EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage
The Symmetrix ID of EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage is displayed.
[Corrective Action]
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should review the port combination for the storage unit at storage_unit_ipaddr, referring to "6.1.1 Creating Definition Files for Combining Ports for SAN Storage" in the "Setup Guide CE".
[Description]
More than one key is specified.
[Corrective Action]
If this message is output during the following operation, after reviewing the content of the XML file specified during the operation, ensure that there is only one entry for the element specified in key, and perform the operation again.
When key is "Pool"
Ensure that only one Pool element is defined.
When key is "VmHosts"
Ensure that only one VmHosts element is defined.
When key is "VmHost(ip=IP address of VM host defined in XML)"
Ensure that only one VmHost element to which an IP address of the VM host defined in the XML is specified for ip is defined.
When key is "VmHost(ip=IP address of VM host defined in XML).Disks"
Ensure that only one Disks tag is defined in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
When key is "VmHost(ip=IP address of the VM host defined in the XML).Disks.Disk(name=Disk resource name defined in XML)"
Ensure that only one Disk element to which the disk resource name defined in the XML is specified for name is defined in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
When key is "VmHost (ip=IP address of the VM host defined in XML).Disks.Disk(path=Device path to the disk resource defined in XML)"
Ensure that only one Disk element to which the device path to the disk resource defined in the XML is specified for path is defined in the VmHost element to which an IP address of the VM host defined in the XML is specified for ip.
[Description]
The port combination of the storage unit of the storage_unit_ipaddr file defined by the SAN storage port combination is not defined in the 2 port combination.
storage_unit_ipaddr
For ETERNUS Storage
The IP address of the admin LAN port of ETERNUS storage is displayed.
For EMC CLARiiON Storage
The IP address of the SP of EMC CLARiiON storage is displayed.
For EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage
The Symmetrix ID of EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage is displayed.
pattern
FC connection pattern file
"FC connection pattern file name.rcxprop" is displayed.
[Corrective Action]
Notify the infrastructure administrator of the information in this message.
Refer to "Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE", and review the port combinations for storage_unit_ipaddr storage unit (as infrastructure manager).
[Description]
The port combination of the storage unit of the storage_unit_ipaddr file defined by the SAN storage port combination is defined using an invalid number of ports.
storage_unit_ipaddr
For ETERNUS Storage
The IP address of the admin LAN port of ETERNUS storage is displayed.
For EMC CLARiiON Storage
The IP address of the SP of EMC CLARiiON storage is displayed.
For EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage
The Symmetrix ID of EMC Symmetrix DMX Storage or EMC Symmetrix VMAX Storage is displayed.
pattern
FC connection pattern file
"FC connection pattern file name.rcxprop" is displayed.
[Corrective Action]
Notify the infrastructure administrator of the information in this message.
Refer to "Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE", and review the port combinations for storage_unit_ipaddr storage unit (as infrastructure manager).
[Description]
The number of columns is not num in the line item of the file displayed in filename.
[Corrective Action]
Check the line item in the file displayed in filename and confirm that the number of columns is num.
[Description]
Field value has not been specified in the line item of the file displayed in filename.
[Corrective Action]
Check the line item in the file displayed in filename and confirm that a field value has been specified.
[Description]
Invalid field value in the line item of the file displayed in filename.
[Corrective Action]
Check the line item in the file displayed in filename and confirm that field value is correct.
"storage_mirroring.rcxprop" is displayed in filename
Check the following:
The RAID group number or TPP number is a hexidecimal of 4 digits starting with 0x.
The virtual storage type is "RAID" or "TPP".
[Description]
In the file displayed in filename, the item definitions for the storage unit of ip-address are duplicated.
item
BOX-ID Storage unit BOX-ID of ETERNUS
RAID Storage unit RAID group number of ETERNUS
TPP Storage unit TPP number of ETERNUS
value
Value of the item where definitions are duplicated
[Corrective Action]
In the file displayed in filename, check that the definitions for the storage unit of ip-address are not duplicated.
"storage_mirroring.rcxprop" is displayed in filename
Take corrective action based on the content of item.
BOX-ID
There are multiple remote site storage unit specified as remote site storage unit. Review the definition.
RAID
The RAID Group number on the local is duplicated. Review the definition.
TPP
The TPP number on the local is duplicated. Review the definition.
[Description]
An incorrect value or time range was specified in option.
One of the following is output in option:
-from
-to
-duration
-from >= -to
[Corrective Action]
Refer to the command reference and specify a correct value or time range in option, then perform the operation again.
For details, refer to "1.7.15 rcxadm logctl".
[Description]
The process process for the log operation failed.
In process, "read", "delete", or "copy" is output.
[Corrective Action]
Check the system log, resolve the cause of the error, and then perform the operation again.
Check if there are any error messages regarding the disk or file system.
Check if there is a quota limit or file system full message.
[Description]
The specified obj is not empty.
[Corrective Action]
Perform the operation again after emptying the specified obj.
[Description]
The resource in obj1 is already used by obj2. When multiple resources are operated using one operation, only the first resource name an inconsistency was detected for is displayed.
[Corrective Action]
When releasing registered resources from resource pools or deleting resource pools forcibly
Perform the operation again, after changing the resource so it is not used.
When VM management software is deleted
Perform the operation again, after changing the resource so it is not used.
If an L-Server is being managed by the VM management software, the VM management software cannot be deleted.
If this message is displayed when deleting the VM management software, delete all L-Servers operating on VM hosts managed by the VM management software (obj1) for deletion.
The VM host under the management of the VM management software that is to be deleted is displayed in resource. When there are multiple VM hosts, an arbitrary VM host will be displayed.
The L-Server created in resource is displayed in obj2. When there are multiple L-Servers, an arbitrary L-Server will be displayed.
When storage management software is deleted
If an L-Server using virtual storage resource is being managed by the storage management software, the storage management software cannot be deleted.
If this message is displayed when deleting the storage management software, delete all L-Servers using virtual storage resource managed by the storage management software (obj1) for deletion.
The virtual storage resource under the management of the storage management software that is to be deleted is displayed in resource. When there are multiple virtual storage resources, an arbitrary virtual storage resource will be displayed.
The L-Server using resource is displayed in obj2. When there are multiple L-Servers, an arbitrary L-Server will be displayed.
If there is a storage pool managed by the storage management software that has virtual storage resources registered, the storage management software cannot be deleted.
If this message is displayed when deleting storage management software, release virtual storage resources managed by the storage management software (obj1) that will be deleted.
The virtual storage resource under the management of the storage management software that is to be deleted is displayed in resource.
When there are multiple virtual storage resources, an arbitrary virtual storage resource will be displayed.
The storage pool in which resource is registered is displayed in obj2. When there are multiple storage pools, an arbitrary storage pool will be displayed.
When a disk resource corresponding to the LUN created in advance has been registered in a storage pool, storage management software corresponding to the disk resource cannot be deleted. Before deleting the storage management software, unregister the disk resource corresponding to the LUN created in advance from the storage pool.
When creating a physical L-Server:
In this case, the following messages will be output in the event log:
When "(create)" follows after resource
The specified physical server resource is already assigned as an L-Server, or registered as a spare server.
When "(Spare)" follows after resource
The physical server resource specified as a spare server is already assigned as an L-Server, or registered as a spare server.
When "(Primary)" follows after resource
The physical server resource specified in the physical server usage change is already assigned as an L-Server, or registered as a spare server.
Specify a physical server resource or resource pool that is already registered, and perform the operation again.
When IP address is displayed in resource
The network resource of the specified IP address has already been allocated to another L-Server. Specify an unused IP address for the network resource, and perform the operation again.
When an address set resource is deleted
Perform the operation again, after changing the resource so it is not used.
If an L-Server using a WWN and a MAC address selected from an address set resource exists, the address set resource cannot be deleted.
If this message is displayed when deleting an address set resource, execute the rcxadm addrset show command to check the WWN or the MAC address in use, then delete all L-Servers for which the WWN and the MAC address are set.
The WWN and the MAC address used by the L-Server are displayed in resource. If multiple WWNs and MAC addresses exist, one WWN or one MAC address is displayed at random.
The address set resource name for deletion is displayed in obj1.
"L-Server" is displayed in obj2.
When a managed server is modified or deleted
Perform the operation again, after changing the resource so it is not used.
If there is a physical L-Server for which the same admin IP address as that of the specified managed server has been set, the managed server cannot be modified or deleted.
If this message is output when modifying a managed server
Change the admin IP address of the physical L-Server displayed in obj2, and then perform the operation again.
If this message is output when deleting a managed server
Delete the physical L-Server displayed in obj2, or release the managed server from the physical L-Server, and then perform the operation again.
The admin IP address used by a physical L-Server is displayed in resource.
The name of the network resource in use is displayed in obj1.
The name of the physical L-Server for which the same IP address as that of the specified managed server has been set, is displayed in obj2.
When a network device is modified or deleted
If necessary, change the resource so it is not used, and then perform the operation again.
[Description]
An error occurred while executing a script registered for external integration.
[Corrective Action]
If other software is integrated into Resource Orchestrator, refer to the manuals for that software and check whether script_name is registered.
If script_name is registered, refer to the manual of that software.
If the integrated software cannot be found, collect this message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
The disk corresponding to the specified diskname is not recognized by vmhost.
In diskname, the name of the disk resource registered with the admin server is displayed.
In vmhost, the name of the VM host registered with the admin server is displayed.
[Corrective Action]
Check and modify the storage settings so that the disk can be recognized by vmhost.
[Description]
The value of item of filename is invalid.
item is NUM_OF_FC
the following is displayed in detail.
please specify the value as 1, 2, or 4
item is BOOT_FC_PORT
the following is displayed in detail.
please specify the value within the range of NUM_OF_FC
When item is STORAGE_0, one of the following is displayed for detail:
please specify the correct format
[Corrective Action]
Notify the infrastructure administrator of the information in this message.
Refer to "Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE", and review the item value (as infrastructure manager)
[Description]
The specified resource value does not exist in the source pool. One of the following is displayed in value.
Resource name
The resource may have been deregistered from the pool or it may have been moved to a different pool.
"" (empty string)
The resource may have been deleted.
[Corrective Action]
Check the content displayed in value, eliminate the cause of the error and then re-execute.
Resource Name
Deselect the value in the resource list, then retry. Alternatively, close the dialog box and try again.
In the case of "" (empty string)
Close the dialog box and try again.
[Description]
A pool that does not exist has been specified as the destination. The destination may have been deleted.
[Corrective Action]
Close the dialog box and check that the destination exists.
[Description]
A type other than a resource pool has been specified in dest, so the transfer is not possible. The resource pool specified at the destination must be the same as the resource type at the source.
[Corrective Action]
Change the destination and then try again.
[Description]
A pool type dest_type has been specified as the destination dest that differs from the pool type source_type for the source, so the transfer is not possible. The resource pool specified at the destination must be the same as the resource type at the source.
[Corrective Action]
Change the destination and then try again.
[Description]
An error occurred while performing the import process. The following information is stored in an error message:
type=type
Resource type where the error occurred (template, folder, pool, network, addrset, image, lserver, user, usergroup, firewall) is displayed.
message=message
Details of the error that occurred are displayed.
If the resource type is pool, addrset, lserver, network, or firewall, the following is also displayed.
name=name
The name specifying the resource where the error occurred is displayed. If the name cannot be determined, id = resource ID is displayed.
Example
(L-Server) : /tenant1/l-platform1/l_server1
The name part is not display for any other type.
[Corrective Action]
Take the following action for each of the error messages:
If this does not resolve the problem, collect this message and troubleshooting data, and contact Fujitsu technical staff.
type is template, folder, pool, network, addrset, user, usergroup
Refer to the message error message, take the appropriate action, then re-import.
type is lserver and the message is ":67154:VM Guest not found"
Use rcxadm config show to view the VM name, host name, and external identifier, then reregister the VM on the import destination.
If the VM is not included in the disk where storage replication was performed, remove the L-Server from the import configuration definition information, then perform import again.
type is lserver and the message is "67154:value:not found"
Use rcxadm config show to determine the resources relevant to the ServerType and value of the L-Server.
ServerType is Virtual, and "VirtualStorage name="value"" is in the relevant value
The virtual storage is not registered in a storage pool that can be viewed from the location where the L-Server is deployed. Check that the following resources (relevant to value in the VM management software registered with Resource Orchestrator) have been correctly registered, then perform import again.
vCenter: Data store name
SCVMM: Cluster Shared Volume name
If the resources are not registered with the VM management software, for example if virtual storage is not included in the disk where storage replication was performed
After removing the relevant L-Server from the configuration definition information for import, perform import again.
type is firewall and the message is "67154:ProvisioningNode(name=fw_device_name):not found"
Check if the network device for fw_device_name is registered in the network pool of the tenant for name.
If it has not been registered, check if fw_device_name has been registered using another name in the server tree. Ensure that it is correctly registered, and then perform import again.
If the network device cannot be registered because it does not exist in the destination environment, delete the name L-Platform, following the procedure described in "15.3 Switchover Operations when Damaged" in the "Operation Guide CE". During the deletion procedure, make a note of the L-Platform name, and delete the L-Platform after the import process is complete.
type is image, and the message is "67154:obj not found"
Check that there is VM management software with an image registered, or a VM host's server registered, if there is not one registered, register one and then perform import again.
In other cases
Refer to the message error message, take the appropriate action, then re-import.
[Description]
A resource identifier for import conflicts with another resource identifier.
The rcxadm config reserve command is not executed in the DR procedure.
[Corrective Action]
Install the manager again. After installation, following the DR procedure, execute the rcxadm config reserve command and the rcxadm config import command.
[Description]
Since the NICs specified in the index index for the L-Server server-name were created before the functions of addition or deletion of NICs were supported, the specified NIC cannot be deleted.
[Corrective Action]
Check the specified values for the NIC index of an L-Server, resolve the cause, and perform the operation again.
[Description]
There are no NICs with the specified MAC addresses mac-address that are allocated to VM guests related to the L-Server server-name.
[Corrective Action]
Check the MAC addresses of NICs from VM management software, and perform the operation again.
[Description]
The IP address of the storage unit has not been registered in the storage management product soft.
[Corrective Action]
Check the following, resolve the cause of the error, and then perform the operation again.
The specified storage unit has been registered in the storage management product soft.
The IP address of the storage unit has been registered in the storage management product soft.
[Description]
Cannot find replication definition.
[Corrective Action]
After checking that the replication definitions have been correctly registered with the storage management product soft, retry.
[Description]
The IP address of the storage apparatus has not been registered in the storage management product soft.
[Corrective Action]
Perform one of the following corrective actions:
After setting the IP address of the storage apparatus in the storage management product soft, execute the command again.
Once the -local option is specified, specify the IP address and Box ID with the -remote option, then retry.
[Description]
The settings of the nth tag_name tag (name) in the definition file are incorrect. In detail_message, a message indicating the cause is displayed. All operations described in the definition file have not been completed.
[Corrective Action]
Refer to the corrective action of the message displayed in detail_message. Remove the cause of error, and execute the operation again.
[Description]
Operations of the nth User tag (user) in the definition file failed. In detail_message, a message indicating the cause is displayed. The user operations described before the user_id that caused an error in the definition file have been completed.
[Corrective Action]
Refer to the corrective action of the message displayed in detail_message. Remove the cause of error, create the definition files for after the user that failed, and execute the operation again.
[Description]
Operations of the nth Tenant tag (tenant) in the definition file failed. The message that is the cause is displayed in detail_message. All operations described in the definition file have not been completed.
[Corrective Action]
Refer to the corrective action of the message displayed in detail_message. Remove the cause of error, and execute the operation again.
[Description]
It is not possible to specify a user group that is used to manage tenants for the user group user_group of users with an infrastructure administrative role or multiple role.
[Corrective Action]
Specify a user group other than a user group used to manage tenants.
[Description]
The option option, which can only be specified once for a user with a tenant administrator role or tenant user role, has been specified multiple times.
[Corrective Action]
Specify only one option.
[Description]
One of following, which cannot be configured, was specified for the role role.
lplatform_user was specified for the role when creating a user.
Only lplatform_user was specified for the role when modifying a user.
[Corrective Action]
Configure the correct role.
When creating a user, specify a role other than lplatform_user.
When specifying lplatform_user, if modifying a user, also specify the tenant user role.
[Description]
One of following roles, which cannot be changed, was specified.
An attempt was made to change from a tenant management role or tenant user role to an infrastructure administrative role or a multiple role.
An attempt was made to change from an infrastructure administrative role or a multiple role to a tenant management role or tenant user role.
[Corrective Action]
When changing a role, specify a role in the following scopes:
When changing a tenant management role or a tenant user role, specify one of these two roles.
When changing an infrastructure administrative role or a multiple role, specify one of these two roles.
[Description]
An attempt was made to create a tenant tenant other than a root folder
[Corrective Action]
Create a tenant in the root folder.
[Description]
The tenant tenant with the same name as that of the user group cannot be created.
[Corrective Action]
For a tenant, specify a name other than the name of the current user group.
[Description]
An L-Platform exists under the tenant tenant.
[Corrective Action]
Check if the specified tenant name is correct. When the tenant name is correct, delete the L-Platform under the tenant.
[Description]
A user exists in the user group user_group used for managing tenants.
[Corrective Action]
Check if the specified tenant name is correct. When the tenant name is correct, delete the users belonging to the user group used for managing tenants.
[Description]
The user group user_group used for managing tenants cannot be changed or deleted.
[Corrective Action]
Check if the specified user group is correct. The user group managing a tenant is deleted, at the same time as the tenant is deleted.
[Description]
Necessary settings have not been configured in the tuning parameter file "file".
In param_names, all parameters that have not been configured are displayed.
If file is the definition file for alive monitoring
"alive_monitoring/definition file name.rcxprop" is displayed.
[Corrective Action]
If file is the definition file for alive monitoring
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should review the settings, referring to "Definition File for Alive Monitoring" in "D.5.1 Definition Files" in the "Setup Guide CE".
[Description]
Failed to create the virtual switch name on server server.
If the target server is a Hyper-V server
Virtual switch indicates the virtual network of Hyper-V.
[Corrective Action]
Take corrective action based on the content of code.
If code is "15" or "1511"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
When using Intel PROSet in Hyper-V, refer to "E.3.5 Advisory Notes for Hyper-V Usage" of the "Setup Guide CE".
If code is "16", "1524", or "1525"
The VM host could not be found.
Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM host has been deleted.
If code is "100", "115", "1512", "1526", "1527", "1528", "1529", or "1531"
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details on changing login account information, refer to "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When using Intel PROSet in Hyper-V, refer to "E.3.5 Advisory Notes for Hyper-V Usage" of the "Setup Guide CE".
If code is "101", "110", "111", "112", "114", "116", or "1509"
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If code is "113" or "1510"
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details on changing login account information, refer to "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If code is "500", "511", "1530", "1532", "1533", "1534", or "1600"
Failed to create the virtual switch as the configuration of the physical network adapter and virtual switch of the VM host/VM management software is not capable of creating the virtual switch. Check the configuration of the physical network adapter and virtual switch of the VM host/VM management software, referring to "7.3 Network Resources" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When using Intel PROSet in Hyper-V, refer to "E.3.5 Advisory Notes for Hyper-V Usage" of the "Setup Guide CE".
If code is "513" or "1601"
Failed to create the virtual switch as the physical network adapter to connect to another virtual switch is in use. Check the network settings of the VM host/VM management software.
Creation of the virtual switch failed as the type (active or standby) of the physical network adapter for connection to another virtual switch is different from that of other virtual switches. Check the physical LAN segment specified in the network configurations and network resources of VM hosts and VM management software.
If code is "514" or "515"
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If code is "1599"
Failed to create the virtual switch as the response from the VM host or VM management software to the admin server is not correct. Check the operation status and network settings of the VM host or VM management software.
When using Intel PROSet in Hyper-V, refer to "E.3.5 Advisory Notes for Hyper-V Usage" of the "Setup Guide CE".
If code is "1602"
Creation of the virtual switch failed because the virtual switch name already exists. Change the virtual switch name of the VM host/VM management software.
When creating network resources using unsupported network configurations for the automatic network configuration, create the network resources manually.
Note that if network resources are to be created using this configuration, specify auto="false" in the Network tag of the XML file that defines the network resource and then retry.
For details on creation of the XML file defining network resources and Network elements, refer to "2.5.1 Creation".
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in code, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to delete the virtual switch name on server server.
If the target server is a Hyper-V server
Virtual switch indicates the virtual network of Hyper-V.
[Corrective Action]
Take corrective action based on the content of code.
As the virtual switch name remains on the server server, check its usage status and if it is no longer necessary, delete the virtual switch from the VM management software.
If code is "15" or "1511"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If code is "16", "1524", or "1525"
The VM host could not be found.
Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM host has been deleted.
If code is "100", "115", or "1512"
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details on changing login account information, refer to "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If code is "101", "110", "111", "112", "114", "116", or "1509"
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If code is "113" or "1510"
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details on changing login account information, refer to "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If code is "520"
Failed to delete the virtual switch. Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Resolve the problem with the VM host/VM management software.
If code is "522"
Failed to delete the virtual switch as the switch is in use. If the virtual switch is not necessary, delete the virtual switch from the VM management software.
If code is "523" or "524"
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in code, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to create the virtual network name on server server.
When the target server is a VMware server
The virtual network indicates a port group on the virtual switch.
[Corrective Action]
Take corrective action based on the content of code.
If code is "15"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If code is "16"
The VM host could not be found.
Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM host has been deleted.
If code is "100" or "115"
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details on changing login account information, refer to "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If code is "101", "110", "111", "112", "114", or "116"
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If code is "113"
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details on changing login account information, refer to "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If code is "610"
Failed to create the virtual network because the virtual network name already exists. Change the virtual network name for the VM host/VM management software.
If code is "611"
Failed to create the virtual network. Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Perform the operation again after resolving the problem with the VM host/VM management software.
If code is "613"
Failed to create the virtual network, as the virtual switch to connect to the virtual network cannot be found. Check the virtual switch of the VM host/VM management software.
If code is "614" or "615"
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in code, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Failed to delete the virtual network name on server server.
When the target server is a VMware server
The virtual network indicates a port group on the virtual switch.
[Corrective Action]
Take corrective action based on the content of code.
As the virtual network name remains on the server server, check its usage status and if it is no longer necessary, delete the virtual network from the VM management software.
If code is "15"
There is no response from the VM host/VM management software to the admin server request. Check the operation status and network settings of the VM host/VM management software.
If code is "16"
The VM host could not be found.
Select [Operation]-[Update] from the ROR console menu to refresh the screen, and check whether the VM host has been deleted.
If code is "100" or "115"
The login account information for the VM host/VM management software entered during registration may not have the required privileges.
Check the privilege status from the VM management software. If the account does not have the required privileges, change the entered values (user name and password) for the login account information to the values for a user with administrative privileges for the VM host/VM management software.
For details on changing login account information, refer to "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If code is "101", "110", "111", "112", "114", or "116"
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If code is "113"
The login account information for the VM host/VM management software that was entered during registration cannot be used to communicate with the VM host/VM management software. The login account information for the VM host/VM management software may have been changed after registration.
Change the entered values (user name and password) for the login account information to the correct values.
For details on changing login account information, refer to "3.2.7 Changing VM Host Login Account Information" or "3.8 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If code is "620"
Failed to delete the virtual network. Check the operation status and network settings of the VM host/VM management software. If operations performed from the VM management software are not executed, there is a problem with the VM host/VM management software. Resolve the problem with the VM host/VM management software.
If code is "622"
Failed to delete the virtual network as the virtual network being used by the VM guest. If the virtual network is not necessary, delete the virtual network from the VM management software.
If code is "623" or "624"
Communication between the admin server and the VM host/VM management software failed. Check the operation status and network settings of the VM host/VM management software.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in code, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
The virtual switch name was not found on the server server.
[Corrective Action]
Perform the operation again after restoring the target virtual switch using the VM management software.
Due to the specification of an external port for the network resource corresponding to the virtual switch, it is necessary to connect to an appropriate physical network adapter. For details, refer to "7.3 Network Resources" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
[Description]
The virtual network name was not found on the server server.
[Corrective Action]
Perform the operation again after restoring the target virtual network using the VM management software.
When the virtual network name has the same name as a network resource
Check the VLAN ID of the network resource using the GUI, and set the same VLAN ID for the virtual network.
When the virtual network name does not have the same name as a network resource
Create a virtual network with the same name as the virtual network created in advance on the server server.
When the target server is a VMware server
The virtual network indicates a port group on the virtual switch.
[Description]
An attempt was made to create a virtual network name assigned with vlanid1; however, a virtual network name assigned with vlanid2 already exists.
[Corrective Action]
Perform the operation again after deleting the previously created virtual network name assigned with vlanid2, or changing the name of the virtual network on registered VM host server.
When the target server is a VMware server
The virtual network indicates a port group on the virtual switch.
[Description]
There are multiple virtual networks assigned with the same vlanid.
[Corrective Action]
Change the virtual network and vlanid combinations so that they are unique between the registered VM hosts.
Use a unique, case-sensitive virtual network name.
When the target server is a VMware server
The virtual network indicates a port group on the virtual switch.
If the VLAN set in the service console or VMkernel network port group and the VLAN set in the port group used for the virtual machine are the same, then the "VMware Exclusion Port Group Definition File" needs to be configured.
Refer to "When Using the Definition for Port Groups Excluded from the Selections for Automatic Network Configuration" in "E.2.2 Preparations" in the "Setup Guide CE" for details.
Also, if multiple pieces of server virtualization software are being used by one manager, then it may be influenced by the settings for the virtual switches, virtual networks, and virtual bridges on another piece of server virtualization software.
When Hyper-V is being used by another server
In the settings for the virtual network to access the VM host through the VLAN, make sure the same VLAN is not set.
If the same VLAN is set, change the VLAN or change the settings so the VLAN is not used.
[Description]
NIC redundancy has not been configured for the combination of NIC (number) on the server server.
In number, the server NIC index numbers to connect with the virtual switches are displayed, separated by commas.
In mac, the MAC address information of the server NIC to connect with the virtual switches is displayed, separated by commas.
If the target server is a Hyper-V server
Virtual switch indicates the virtual network of Hyper-V.
When creating a virtual switch, it is connected to NIC (number) on the server server.
Redundancy may not have been configured for the NIC(number) in advance.
[Corrective Action]
If the target server is a Hyper-V server
Configure NIC redundancy using the combination of NIC (number) on the server server.
If NIC redundancy has been already configured, the communication between admin server and server server have failed and NIC redundancy information may have not been obtained.
Refer to the explanation in "Message number 67192" in the "Messages VE".
When creating network resources using unsupported network configurations for the automatic network configuration, create the network resources manually.
Note that if network resources are to be created using this configuration, specify auto="false" in the Network tag of the XML file that defines the network resource and then retry.
For details on creation of the XML file defining network resources and Network elements, refer to "2.5.1 Creation".
[Description]
The virtual switch name1 cannot be created, as there is a virtual switch, name2, for NIC(number) on the server server.
In number, the server NIC index numbers to connect with the virtual switches are displayed, separated by commas.
If the target server is a Hyper-V server
Virtual switch indicates the virtual network of Hyper-V.
[Corrective Action]
Delete the virtual switch name2 or change the name name2 to the virtual switch name1.
[Description]
The virtual switch name already exists on a NIC other than NIC(number).
In number, the server NIC index numbers to connect with the virtual switches are displayed, separated by commas.
If the target server is a Hyper-V server
Virtual switch indicates the virtual network of Hyper-V.
[Corrective Action]
Either delete the virtual switch name created on the interface, excluding NIC(number), or change the name of the virtual switch.
[Description]
When server is a physical server
The external connection port of the switch specified for the network resource name and NICnumber are not connected.
When server is a VM host
The external connection port of the switch specified in the network resource name is not connected to the NICnumber used for the virtual network manually created by the user in advance.
[Corrective Action]
When server is a physical server
Check the details related to the causes of the description above, and specify a NIC which can be connected with the network resource.
When server is a VM host
Check the details related to the causes of the description above, and create the virtual network again. Create a network resource again after correcting the external connection port.
[Description]
The specified configuration is unavailable for automatic network configuration.
In detail, the following detailed information is displayed:
"different types of LAN switch blades model"
In the specified LAN switch blades on the external connection ports for the network resource, different models of LAN switch blades are selected in the combination model for the same chassis.
The model names of the LAN switch blades are output in model, separated by commas(",").
"Physical NIC team of virtual switch name on the server server is not supported"
The physical NIC teaming configuration of the already created virtual switch name is not supported.
Physical NICs have not been connected with the virtual switch name. Otherwise teaming of three or more physical NICs has been performed for the virtual switch name.
"Outside external port range:exdetail"
The external connection ports specified for the network resources are outside the range for automatic network configuration.
In exdetail, the following information is output:
The information for some items may not be obtained. In that case, "-" is displayed for the corresponding item.
(port=(External_connection_port,LAN_switch_blade_name)[/(...,...)],vmhost=Destination_VM_host_name,chassis=chassis_name) |
port
A pair of the external connection port number and the LAN switch blade name specified for the network resource is output.
When multiple port information is output, each piece of information is output separated by a slash("/").
vmhost
The name of the destination VM host is output.
chassis
The name of the chassis is output.
"Combination of external ports:exdetail"
The combination of the external connection ports specified for the network resource is out of the configuration for automatic network configuration.
In exdetail, the following information is output:
The information for some items may not be obtained. In that case, "-" is displayed for the corresponding item.
(port=(External_connection_port,LAN_switch_blade_name)[/(...,...)],vmhost=Destination_VM_host_name,chassis=chassis_name) |
port
A pair of the external connection port number and the LAN switch blade name specified for the network resource is output.
When multiple port information is output, each piece of information is output separated by a slash("/").
vmhost
The name of the destination VM host is output.
chassis
The name of the chassis is output.
"Specified external port is not suitable for an existing composition:exdetail1,exdetail2"
The external connection port specified for the network resource does not match the configuration of the external connection port specified for the existing network resource.
In exdetail1, the following information is output as the network resource that was specified for creation:
The information for some items may not be obtained. In that case, "-" is displayed for the corresponding item.
(port=(External_connection_port,LAN_switch_blade_name)[/(...,...)],chassis=chassis_name) |
port
A pair of the external connection port number and the LAN switch blade name specified for the network resource is output.
When multiple port information is output, each piece of information is output separated by a slash("/").
chassis
The name of the chassis is output.
In exdetail2, the following information is output as the existing network resource which was the cause of the relevant problem:
The information for some items may not be obtained. In that case, "-" is displayed for the corresponding item.
(port=(External_connection_port,LAN_switch_blade_name)[/(...,...)],vlanid=vlanid,chassis=chassis_name) |
port
A pair of the external connection port number and the LAN switch blade name specified for the network resource is output.
When multiple port information is output, each piece of information is output separated by a slash("/").
vlanid
The vlanid specified for the network resource is output.
chassis
The name of the chassis is output.
"Not supported chassis:exdetail"
The chassis to be used is not supported.
In exdetail, the following information is output:
(model=Model_name_of_chassis) |
model
The model name of the chassis is output.
"External port cannot connect to server:exdetail"
An external connection port connectible to the deployment destination VM host has not been specified for the network resource.
In exdetail, the following information is output:
The information for some items may not be obtained. In that case, "-" is displayed for the corresponding item.
(vmhost=Destination_VM_host_name) |
vmhost
The name of the destination VM host is output.
"NIC is not recognized on the host:exdetail"
The NIC on the server for which the external connection port specified in the network resource name is not recognized.
In exdetail, the following information is output:
(server=(Server_name,index_number_of_physical_link_information)) |
server
The NIC number on the deployment destination server which is not recognized as the destination server name is output.
[Corrective Action]
Check the configurations supported for automatic network configuration, and resolve the error.
Take corrective action based on the content of detail.
"different types of LAN switch blades model"
For each chassis, check that the same model of the LAN switch blade is specified on the external connection ports for the network resource.
For LAN switch blades, the same model must be used in the same chassis, according to the following model combinations:
When the chassis is a BX900
CB1 and CB2
CB3 and CB4
CB5 and CB6
CB7 and CB8
When the chassis is a BX600
NET1 and NET2
NET3 and NET4
When the chassis is a BX400
CB1 and CB2
CB3 and CB4
"Physical NIC team of virtual switch name on the server server is not supported"
Create the virtual network on the server server again.
"Outside external port range:exdetail"
Confirm that each of the external connection ports specified for the network resource is selected according to the following model combination in the same chassis:
If no external connection port is displayed, check all network resources connected to the L-Server.
When the chassis is a BX900
CB1 and CB2
CB3 and CB4
CB5 and CB6
CB7 and CB8
When the chassis is a BX600
NET1 and NET2
NET3 and NET4
When the chassis is a BX400
CB1 and CB2
CB3 and CB4
For details, refer to "2.6 Registering Network Resources" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
"Combination of external ports:exdetail"
Confirm that each of the external connection ports specified for the network resource is selected according to the following model combination in the same chassis:
If no external connection port is displayed, check all network resources connected to the L-Server.
When the chassis is a BX900
CB1 and CB2
CB3 and CB4
CB5 and CB6
CB7 and CB8
When the chassis is a BX600
NET1 and NET2
NET3 and NET4
When the chassis is a BX400
CB1 and CB2
CB3 and CB4
For details, refer to "2.6 Registering Network Resources" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
"Specified external port is not suitable for an existing composition:exdetail1,exdetail2"
Check if the configuration of the specified external connection port specified for the network resource matches that of the external connection port specified for the network resource that has been already created.
If no external connection port is displayed, check both network resources to be connected to the L-Server and existing network resources.
"Not supported chassis:exdetail"
Check if the chassis to be used is supported.
"External port cannot connect to server:exdetail"
Check if the external connection port connectible to the deployment destination VM host has been specified for the network resource.
If multiple network resources are connected to the deployment target L-Server, check the external connection ports of all network resources.
If no destination VM host name is displayed, check the external connection ports of all network resources to be connected to the L-Server.
"NIC is not recognized on the host:exdetail"
Confirm that the port information of individual servers and LAN switch blades is correctly recognized from the server tree in the ROR console.
When creating network resources using unsupported network configurations for the automatic network configuration, create the network resources manually.
Note that if network resources are to be created using this configuration, specify auto="false" in the Network tag of the XML file that defines the network resource and then retry.
For details on creation of the XML file defining network resources and Network elements, refer to "2.5.1 Creation".
[Description]
Processing was stopped, as errors were detected in the values specified in the definition file displayed in filename.
If filename is an XML definition for server NIC definition file
One of the following is displayed in item:
"NIC index"
There is an error in the value specified for the NIC index.
"NIC redundant"
There is an error in the value specified in the active or standby NIC type.
"PhysicalLANSegment name"
There is an error in the value specified for physical LAN segment name.
If filename contains "alive_monitoring"
There is an error in the value specified in the definition file for alive monitoring.
[Corrective Action]
If filename is an XML definition for server NIC definition file
Perform the operation again after reviewing the specified values of the XML definition of the server NIC definition files, and correcting the definition.
Take corrective action based on the content of item.
"NIC index"
Review the value specified for the NIC index.
"NIC redundant"
Review the values specified in the active or standby NIC values.
"PhysicalLANSegment name"
Review the value specified for the physical LAN segment name.
If filename contains "alive_monitoring"
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should review the settings, referring to "Definition File for Alive Monitoring" in "D.5.1 Definition Files" in the "Setup Guide CE".
[Description]
There is an inconsistency in the attribute values between item and element in the XML definition indicated in file_path.
[Corrective Action]
Take corrective action based on the content of item.
"file name"
Review the relationship between the XML definition file name indicated in file_path and the attribute value of the element element.
For details, refer to "2.11 Server NIC Definitions".
[Description]
The process was aborted for the following reasons:
If automatic VLAN setting is enabled for the external port, specify the member port port that makes up the link aggregation of the LAN switch blade switch in the external port of the physical port.
[Corrective Action]
When specifying the ports that make up the link aggregation in the external port
Specify the link aggregation group name in the lag attribute of the NetworkSwitchPort tag in the network resource XML definitions
If a member port that makes up a link aggregation has been incorrectly specified as the physical port in the external port
Review the physical port number specified in the number attribute of the NetworkSwitchPort tag in the network resource XML definitions.
[Description]
There is an error in the ruleset ruleset_name.
In ruleset_name, the name of the ruleset is displayed.
In detail, the following detailed information is displayed:
"duplicate"
A duplicate ruleset name has been used.
"not found"
The corresponding ruleset does not exist.
"name too long"
The ruleset name exceeds the maximum length.
"name error"
The ruleset name contains invalid characters.
[Corrective Action]
The tenant administrator or the tenant user should notify the infrastructure administrator of the information in this message.
The infrastructure administrator should take the corrective action according to the information displayed in detail.
"duplicate"
Change the folder name corresponding to the duplicate ruleset name to a name that is unique on the system.
For details on the folders for rulesets, refer to "Creating a Folder for Registration Rulesets" in "4.2.4.9 When Automatically Configuring Network Devices" in the "Setup Guide CE".
"not found"
When this error is output while operating an L-Platform
Change the ruleset name specified in the parameter file (default_param.prm) to a valid ruleset name.
When this error is output while creating a network resource
Change the ruleset name specified in the relevant XML file to a valid ruleset name.
"name too long"
Change the ruleset name to one with 32 characters or less.
"name error"
Specify a ruleset name that begins with an alphanumeric character and consists of alphanumeric characters, hyphens ("-"), or underscores("_").
[Description]
One of the following files contains an error:
Parameter file
File storing the information from when an L-Platform including a firewall was created
Interface configuration file for the network device
In ruleset_name, the name of the ruleset is displayed.
In detail, the following detailed information is displayed:
"creation of file (filename) failed"
Creation of the file filename has failed.
The name of the file storing the information from when an L-Platform including a firewall was created is displayed in filename.
"deletion of file (filename) failed"
Deletion of the file filename has failed.
The name of the file storing the information from when an L-Platform including a firewall was created is displayed in filename.
"copying of file (filename) failed"
Copying of the file filename has failed.
One of the names of the files is displayed in filename.
Parameter file
File storing the information from when an L-Platform including a firewall was created
"error in format of file (filename)"
Parsing of the file filename has failed.
One of the names of the files is displayed in filename.
Parameter file
File storing the information from when an L-Platform including a firewall was created
Interface configuration file for the network device
"accessing file (filename) failed"
Access to the file filename has failed.
One of the names of the files is displayed in filename.
Parameter file
Interface configuration file for the network device
[Corrective Action]
The tenant administrator or tenant user should take corrective action according to the information displayed in detail.
"accessing file (filename) failed"
Execute the same operation again.
When the same errors are displayed, notify the infrastructure administrator of the information in this message.
The infrastructure administrator should check the following and resolve the cause of the error.
Access privileges for the files in the directory (including its child directories) where the ruleset ruleset_name is registered
That there is sufficient disk space available
After completing the corrective actions above, request the tenant administrator or the tenant user to execute the same operation again.
When the same errors are displayed, notify the infrastructure administrator of the information in this message.
If detail is something other than the above, the tenant administrator or the tenant user should notify the infrastructure administrator of the information in this message.
The infrastructure administrator should take the corrective action according to the information displayed in detail.
"error in format of file (filename)"
Correct the parameter file or the network device interface configuration file.
detail in all other cases
Check the following and resolve the cause.
Access privileges for the files in the directory (including its child directories) where the ruleset ruleset_name is registered
That there is sufficient disk space available
After completing the corrective actions above, request the tenant administrator or the tenant user to execute the same operation again.
When the same errors are displayed, notify the infrastructure administrator of the information in this message.
[Description]
There is an error in the script list scriptlist_name.
In ruleset_name, the name of the ruleset is displayed.
In scriptlist_name, the script list name is displayed.
In detail, the following detailed information is displayed:
"not found"
The script list scriptlist_name was not found.
"file mode error"
A directory has been specified for the script list scriptlist_name.
"access error"
Accessing of the script list scriptlist_name has failed.
[Corrective Action]
The tenant administrator or tenant user should take corrective action according to the information displayed in detail.
"access error"
Execute the same operation again.
When the same errors are displayed, notify the infrastructure administrator of the information in this message.
The infrastructure administrator should check the following and resolve the cause of the error.
Access privileges for the files in the directory (including its child directories) where the ruleset ruleset_name is registered
That there is sufficient disk space available
After completing the corrective actions above, request the tenant administrator or the tenant user to execute the same operation again.
When the same errors are displayed, notify the infrastructure administrator of the information in this message.
If detail is something other than the above, the tenant administrator or the tenant user should notify the infrastructure administrator of the information in this message.
The infrastructure administrator should take the corrective action according to the information displayed in detail.
"not found"
In the directory where the ruleset ruleset_name is registered, create the script list scriptlist_name, and the script specified in the script list scriptlist_name.
"file mode error"
Make sure to create the script list scriptlist_name in text format.
[Description]
There is an error in the descriptions in the script list scriptlist_name.
In ruleset_name, the name of the ruleset is displayed.
In scriptlist_name, the script list name is displayed.
In detail, the following detailed information is displayed:
"line over"
The number of script lines specified in the script list scriptlist_name exceeds the limit of 100.
"operand (operand_name) incorrect. line=n"
The operand operand_name in the relevant line n of the script list scriptlist_name is not correctly specified.
In operand_name, the name of the operand which is not correctly specified is displayed.
When operand_name is "group"
More than one "group" is specified.
There is an error in the value specified for the operand "group".
The operand group has been specified in the rule sets used for network resources.
If there are more than one script groups that have been grouped with the same number in the script list scriptlist_name, the number of scripts in each group does not match.
When operand_name is "-"
The operand has not been specified using the "operand name = value" format.
When the operand_name is not the above
The operand_name operand has been specified more than once.
The value specified in operand_name is invalid.
The operand_name is not a valid operand name.
In n, the line number of the script list scriptlist_name at which an error occurred is displayed.
"script path error. line=n"
The script path specified in the script list scriptlist_name is incorrect.
In n, the line number of the script list scriptlist_name at which an error occurred is displayed.
"no valid lines found"
There is no script specified in the script list scriptlist_name.
[Corrective Action]
The tenant administrator or the tenant user should notify the infrastructure administrator of the information in this message.
The infrastructure administrator should take the corrective action according to the information displayed in detail.
"line over"
Correct the number of script lines specified in the script list file scriptlist_name so it is within 100 lines.
"operand (operand_name) incorrect. line=n"
Take corrective action based on the content of operand_name.
When operand_name is "group"
If multiple operand groups have been specified, make adjustments so that only one operand group is left.
If the value specified in group is invalid, specify a valid value.
If operand groups have been specified in the rule sets for network resources, delete the operand group.
If there are more than one script groups that have been grouped with the same number in the script list scriptlist_name, and the numbers of scripts in each of the script groups are different, adjust so the number of scripts is the same.
When operand_name is "-"
Specify the operand using the format "operand name = value" in the line n of the script list scriptlist_name.
When the operand_name is not the above
If multiple operand operand_name have been specified, make adjustments so that only one operand operand_name is left.
If the value specified in operand_name is invalid, specify a valid value.
If the operand name of the operand_name operand is incorrect, specify a correct operand name or delete the operand_name operand.
"script path error. line=n"
Correct the script path specified in the script list scriptlist_name.
"no valid lines found"
Specify scripts to be executed in the script list scriptlist_name.
[Description]
There is an inconsistency between the content described in the script list scriptlist_name and the descriptions in the create script list.
In ruleset_name, the name of the ruleset is displayed.
In scriptlist_name, the script list name is displayed.
In detail, the following detailed information is displayed:
"group device. line=n"
The following do not match:
The number of the grouped scripts with the same group number in the create script list
The number of the grouped scripts with the same group number in the script list scriptlist_name
In n, the line number of the script list scriptlist_name at which an error occurred is displayed.
"group number. line=n"
The group numbers of the following scripts do not match:
The group number of the grouped scripts specified in the create script list
The group number of the grouped scripts specified in the script list scriptlist_name
In n, the line number of the script list scriptlist_name at which an error occurred is displayed.
When n is "0", the group number of the grouped script specified in the create script list is not specified in the script list scriptlist_name.
"script path. line=n"
The paths of the following scripts do not match:
The path of the script specified in the create script list
The path of the script specified in the script list scriptlist_name
In n, the line number of the script list scriptlist_name at which an error occurred is displayed.
When n is "0", the path of the script specified in the create script list is not specified in the script list scriptlist_name.
[Corrective Action]
The tenant administrator or the tenant user should notify the infrastructure administrator of the information in this message.
The infrastructure administrator should take the corrective action according to the information displayed in detail.
"group device. line=n"
Correct the number of the grouped scripts with the same group number specified in the script list scriptlist_name so that it is the same as the one specified in the create script list.
"group number. line=n"
Correct the group number of the grouped scripts specified in the script list scriptlist_name so that it is the same as the one specified in the create script list.
"script path. line=n"
Correct the script path specified in the script list scriptlist_name so that it matches the script path specified in the create script.
[Description]
There is an error in the file used by execution of the script list scriptlist_name.
In ruleset_name, the name of the ruleset is displayed.
In scriptlist_name, the script list name is displayed.
In detail, the following detailed information is displayed:
"file (file_name) not found. line=n"
The file file_name specified in the script list scriptlist_name was not found.
In file_name, one of the following names is displayed.
Script
Command file
Parameter file
In n, the line number of the script list scriptlist_name at which an error occurred is displayed.
"file (file_name) access error. line=n"
Access to the file file_name specified in the script list scriptlist_name has failed.
In file_name, one of the following names is displayed.
Script
Command file
Parameter file
In n, the line number of the script list scriptlist_name at which an error occurred is displayed.
"file type of file (file_name) incorrect. line=n"
A directory is specified in the file file_name that is specified in the script list scriptlist_name.
In file_name, one of the following names is displayed.
Script
Command file
Parameter file
In n, the line number of the script list scriptlist_name at which an error occurred is displayed.
[Corrective Action]
The tenant administrator or tenant user should take corrective action according to the information displayed in detail.
"file (file_name) access error. line=n"
When the deletion of network resources has been performed
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should log directly into the network device specified in the line n in the script list scriptlist_name and delete the definition manually.
For details on how to log into a network device and how to delete definitions, refer to the manual for the network device.
When operations other than the above operation have been performed
Execute the same operation again.
When the same errors are displayed, notify the infrastructure administrator of the information in this message.
The infrastructure administrator should check the following and resolve the cause of the error.
Access privileges for the files in the directory (including its child directories) where the ruleset ruleset_name is registered
That there is sufficient disk space available
After completing the corrective actions above, request the tenant administrator or the tenant user to execute the same operation again.
When the same errors are displayed, notify the infrastructure administrator of the information in this message.
If detail is something other than the above, the tenant administrator or the tenant user should notify the infrastructure administrator of the information in this message.
The infrastructure administrator should take the corrective action according to the information displayed in detail.
"file (file_name) not found. line=n"
Create the file filename specified in the script list scriptlist_name.
"file type of file (file_name) incorrect. line=n"
Create the file filename specified in the script list scriptlist_name in text format.
[Description]
The network device device_name for executing the script list scriptlist_name cannot be used.
In device_name, the name of the network device is displayed (sometimes it may not be displayed).
In ruleset_name, the name of the ruleset is displayed.
In scriptlist_name, the script list name is displayed.
In detail, the following detailed information is displayed:
"not found. line=n"
The network device device_name specified in the script list scriptlist_name has not been registered.
In n, the line number of the script list scriptlist_name at which an error occurred is displayed.
"cannot be selected. line=n"
There are no network devices for executing the scripts specified in the script list scriptlist_name.
The following causes are possible:
The network device corresponding to the model name or apparatus name in the rule set ruleset_name and the vendor name is not registered in the network pool.
A network device that matches the network device configuration (redundant/non-redundant) that is specified in the script list scriptlist_name is not registered in the network pool.
A network device that can be selected for automatic setting does not exist in the network pool.
In n, the line number of the script list scriptlist_name at which an error occurred is displayed.
"not registered in network pool. line=n"
The network device device_name that executes the scripts specified in the script list scriptlist_name has not been registered in the network pool.
In n, the line number of the script list scriptlist_name at which an error occurred is displayed.
[Corrective Action]
The tenant administrator or the tenant user should notify the infrastructure administrator of the information in this message.
The infrastructure administrator should take the corrective action according to the information displayed in detail.
"not found. line=n"
Register the network device device_name specified in the script list scriptlist_name.
"cannot be selected. line=n"
Follow the instructions below:
Check that the model name (or the device name) and the vendor name specified in the ruleset ruleset_name match the model name (or the device name) and the vendor name of the network devices that have been registered in the network pool.
Register a network device in the network pool that matches the network device configuration (redundant/non-redundant) that is specified in the script list scriptlist_name. If one is already registered, check the redundancy configuration (group ID of network configuration information) of the network device that is registered in the network pool.
Refer to "Network Configuration Information" for information about network configuration information.
Use the rcxadm netdevice show command to check the status of the network device registered in the network pool, then make it so that it can be selected for automatic setting.
If the operational status (Status) of the network device is other than "normal"
Remove the cause of the error in the network device, make sure that the operational status (Status) of the network device is "normal", and retry.
If the maintenance mode (maintenance) of the network device is "ON"
Retry after the maintenance tasks on the network device are complete.
If the automatic setting selectabilty status (AutoConfiguration) of the network device is "false"
If "false" (not the target of auto-configuration) has been set for auto-configuration information for network device (the AutoConfiguration element) when registering or modifying the network configuration information of network devices
Perform modification using the rcxadm netdevice set command so that the corresponding network device can be selected as the target of auto-configuration.
For details on the rcxadm netdevice command, refer to "1.3.6 rcxadm netdevice".
In other cases
Before this message was output, script execution on the same network device had failed, as notified by the following messages:
- "Message number 42751"
- "Message number 62760"
- "Message number 67999"
Based on the message that was output, identify the cause of the script execution error on the network device and take the relevant corrective action.
After taking corrective action, perform modification using the rcxadm netdevice set command so that the corresponding network device can be selected as the target of auto-configuration.
For details on the rcxadm netdevice command, refer to "1.3.6 rcxadm netdevice".
"not registered in network pool. line=n"
Register the network device device_name, which can execute the script specified in the script list scriptlist_name, in the network pool.
[Description]
There is an error in the status of the network device device_name for executing the script list scriptlist_name.
In device_name, the network device name is displayed.
In ruleset_name, the name of the ruleset is displayed.
In scriptlist_name, the script list name is displayed.
In n, the line number of the script list at which an error occurred is displayed.
One of the following network device statuses is displayed in status:
"error"
The network device device_name that executes the scripts specified in the script list scriptlist_name is not in the normal state.
"maintenance mode"
The network device device_name for executing the scripts specified in the script list scriptlist_name is undergoing maintenance.
"unavailable for auto-config"
The network device device_name is unavailable for automatic configuration because execution of the scripts on the device used for executing the scripts specified in the script list scriptlist_name has failed and corrective action is being taken.
[Corrective Action]
The tenant administrator or the tenant user should notify the infrastructure administrator of the information in this message.
The infrastructure administrator should take the corrective action according to the information displayed in detail.
"maintenance mode"
After performing the maintenance tasks on the device_name network device, use the rcxadm netdevice set command to cancel the maintenance mode for the device_name network device.
For details on the rcxadm netdevice command, refer to "1.3.6 rcxadm netdevice".
"error"
Check the status of the network device device_name that executes the scripts specified in the script list scriptlist_name, and then resolve the cause of the error.
"unavailable for auto-config"
If "false" (not the target of auto-configuration) has been set for auto-configuration information for network device (the AutoConfiguration element) when registering or modifying the network configuration information of network devices
Perform modification using the rcxadm netdevice set command so that the corresponding network device can be selected as the target of auto-configuration.
For details on the rcxadm netdevice command, refer to "1.3.6 rcxadm netdevice".
In other cases
Before this message was output, script execution on the same network device device_name had failed, as notified by the following messages:
Based on the message that was output, identify the cause of the script execution error on the network device device_name and take the relevant corrective action.
After taking corrective action, perform modification using the rcxadm netdevice set command so that the corresponding network device device_name can be selected as the target of auto-configuration.
For details on the rcxadm netdevice command, refer to "1.3.6 rcxadm netdevice".
[Description]
The resource type of the network device device_name that executes the scripts specified in the script list scriptlist_name is incorrect.
In ruleset_name, the name of the ruleset is displayed.
In scriptlist_name, the script list name is displayed.
In device_name, the network device name is displayed.
In n, the line number of the script list scriptlist_name at which an error occurred is displayed.
[Corrective Action]
The tenant administrator or the tenant user should notify the infrastructure administrator of the information in this message.
The infrastructure administrator should confirm that the network device device_name has been registered with the correct resource type specified.
[Description]
The switch connected using the NIC number physical_nic_number of the target server server_name could not be found.
In server_name, the name of the server is displayed.
In num, the NIC number is displayed.
In ruleset_name, the name of the ruleset is displayed.
In scriptlist_name, the script list name is displayed.
In n, the line number of the script list scriptlist_name at which an error occurred is displayed.
[Corrective Action]
The tenant administrator or the tenant user should notify the infrastructure administrator of the information in this message.
The infrastructure administrator should check if the switch connected using the NIC number physical_nic_number of the target server server_name has been registered.
If it has been registered, export the network configuration information using the rcxadm netconfig export command, and then check the link information of the switch and the NIC number physical_nic_number of the target server server_name.
For details on the rcxadm netconfig command, refer to "1.3.7 rcxadm netconfig".
Refer to "2.6 Network Configuration Information" for information about network configuration information.
[Description]
The process was aborted because an error occurred while executing the script list scriptlist_name.
In ruleset_name, the name of the ruleset is displayed.
In scriptlist_name, the script list name is displayed.
In detail, the following detailed information is displayed:
"scripts execution error. device=device_name result=code line=n"
An error occurred while executing the script list scriptlist_name.
In device_name, the network device name is displayed.
In code, the return value of the script is displayed.
04
An error that allows re-execution of the script (such as disconnection and timeout) has occurred.
In Other Cases
An error that does not allow re-execution of the script (any other cases) has occurred.
In n, the line number of the script list scriptlist_name at which an error occurred is displayed.
"execution timeout. device=device_name line=n"
Timeout occurred while executing the script list scriptlist_name.
In device_name, the network device name is displayed.
In n, the line number of the script list scriptlist_name at which timeout occurred while executing the script is displayed.
This message may be displayed when there are errors in the network configuration information, specifically when "L2-Switch" has been specified for the "Type" element, and the "Tenant" element has been specified.
[Corrective Action]
When the following two conditions are met, the tenant administrator or tenant user should execute the operation again:
When scriptlist_name is "create.lst", "connect.lst", or "modify.lst"
When detail is "scripts execution error. device=device_name result=04 line=n"
In other cases, or when the problem persists even after re-execution, notify the infrastructure administrator of the operation performed when the error occurred, and the information in this message.
The infrastructure administrator should check for the following mistakes.
In the network configuration information for the network device in question, check for the following mistakes:
"L2-Switch" has been specified for the Type element
The Tenant element has been specified
If either of the above mistakes is found, delete the Tenant element in the network configuration information of the network device in question, and change the network device settings using the rcxadm netdevice modify command.
The network device in question can be identified from the network device name which is indicated in detail or described in the script list scriptlist_name.
For details on the rcxadm netdevice modify command, refer to "1.3.6 rcxadm netdevice".
Refer to "2.6 Network Configuration Information" for information about network configuration information.
If this message is output when operating an L-Platform, check if there is an error in the following files:
[Windows]
Installation_folder\Manager\etc\scripts\network_resource\Unm_network_setting.xml
[Linux]
/etc/opt/FJSVrcvmr/scripts/network_resource/Unm_network_setting.xml
For details on the interface configuration file of network devices, refer to "2.15 Network Device Interface Configuration File".
In other cases, the infrastructure administrator should take corrective action according to the information displayed in detail.
"scripts execution error. device=device_name result=code line=n"
Check the network device and the communication path to the network device, and then remove the cause of the error.
If deleting of the definition of a network device for which a definition has been configured by execution of the script is necessary, log into the network device directly and delete the definition manually.
For details on how to log into a network device and how to delete definitions, refer to the manual for the network device.
"execution timeout. device=device_name line=n"
Identify the time-consuming process occurring during execution of the script and take corrective action accordingly.
When redoing the operation after taking corrective action, first make sure that changes have been made using the rcxadm netdevice show command so that the network device can be selected automatically.
If it cannot be selected as a target of auto-configuration, perform modification using the rcxadm netdevice set command so that the corresponding network device can be selected as a target of auto-configuration.
For details on the rcxadm netdevice command, refer to "1.3.6 rcxadm netdevice".
[Description]
The status of the network device nodeid has changed to status.
One of the following is displayed in cause:
"Ping unreachable"
The network device is not responding to the PING for monitoring active/inactive status.
"SNMP unreachable"
The network device does not respond to SNMP monitoring of status.
[Corrective Action]
Check the state of the network device nodeid.
Take corrective action based on the content displayed for cause.
"Ping unreachable"
Identify the cause that prevents the network device from responding to PING and take corrective action accordingly.
If there is no problem in the network device, it is likely that an error is occurring in the communication path to the network device. Check the network devices on the communication path.
"SNMP unreachable"
Identify the cause that prevents the network device from responding to SNMP and take corrective action accordingly.
If there is no problem in the network device, it is likely that an error is occurring in the communication path to the network device. Check the network devices on the communication path.
[Description]
Setting of the redundancy configuration of the network device has failed.
The same group ID cannot be set for network devices whose vendor name and device name are different.
In device, the network device names registered using the same group ID are displayed. When multiple network devices have been registered, they are displayed separated by commas (",").
[Corrective Action]
Check the vendor names and device names of the network devices, specify a correct group ID for each of them, and perform the operation again.
For details on the vendor names and device names of network devices, refer to "4.2.4.8 When Registering Network Devices as Resources" of the "Setup Guide CE".
[Description]
Setting of login information for the network device device has failed.
Multiple sets of login information with the same privileges and tenant name cannot be defined for a network device.
In authority, privileges of the login information are displayed.
In authority, the tenant name of the login information is displayed.
[Corrective Action]
Specify the correct privileges and tenant name, then perform the operation again.
