This section explains the 61XXX message series.
[Description]
When creating the L-Server or changing the network configuration, there are not enough address type included in name.
When the address type is IPv4
The name of the network resource is displayed in name.
When the address type is MAC or WWN
The name of address set resource is displayed in name.
[Corrective Action]
When the address type is IPv4
Take one of the following actions:
Delete IP addresses that are not to be managed.
Create a new network resource.
Extend the subnet address.
Delete L-Servers that are not needed.
When the address type is MAC or WWN
Create a new address set resource.
Delete L-Servers that are not needed.
[Description]
When creating a physical L-Server, the network resource of the management LAN is not connected.
The physical L-Server must be connected to a management LAN.
[Corrective Action]
Specify so a network resource of the management LAN is connected to the NIC of the physical L-Server, then retry.
[Description]
There is a conflict between value and the address_type of obj.
The following causes are possible:
The specified value overlaps with the address_type of obj
The value of an already registered obj is incorrect
One of the following is displayed in address_type:
IP address
MAC address
Network address
One of the following is displayed in obj:
Admin server
Indicates an admin server.
Resource name
Indicates a registered resource.
Subnet name
Indicates a registered subnet.
[Corrective Action]
When the specified value overlaps with the address_type of obj
Perform the operation again after correcting the specified value.
When the value of an already registered obj is incorrect
Perform the operation again after changing the value of obj.
When this message is displayed during creation of a network resource for which the Admin LAN type is set
Select [Create Resource]-[Using existing admin subnet] to create a resource.
[Description]
Refer to the explanation in "Message number 61162" in the "Messages VE".
[Corrective Action]
Refer to the explanation in "Message number 61162" in the "Messages VE".
[Description]
The power of the L-Server server_name has not been stopped.
The name of the L-Server is displayed in server_name.
[Corrective Action]
Stop the power of the L-Server. Then perform the operation again.
[Description]
The I/O device used for allocation of the server profile on the server server_name was not found.
When creating a physical L-Server, the server name selected when creating the L-Server will be displayed in server_name.
[Corrective Action]
Hardware requirements may not have been met.
For details, refer to "Table 1.50 Required Hardware" of "1.5 Hardware Environment" in the "Setup Guide CE".
[Description]
The address specified for the server server_name already exists.
An address that is the same as one already in use may have been specified.
In server_name, the name of the server is displayed.
When the specified address is that of external software, the name of the external software is displayed in external_software.
In detail, a detailed message is displayed.
[Corrective Action]
Specify an unused address resource, and perform the operation again.
When the error occurs even when an unused address resource is specified, part of the external software information may be incorrect.
Refer to the external software information, and check whether or not the same address is included in the information.
If incorrect information remains, delete the information, and then perform the operation again.
When using the server as a current server, perform the following operations to set a unique address, and then perform the operation again:
Set the address resource as being outside the range
Use the current server as an L-Server
[Description]
When external_software is VIOM
The address specified for the server server_name is outside the range that is available for use.
In server_name, the name of the server is displayed.
In detail, a detailed message is displayed.
[Corrective Action]
Please change the VIOM settings so that the address (MAC address or WWN) displayed in detail is included in the range that is available for use.
[Description]
The server profile profile_name is assigned to another server.
In profile_name, the name of the server profile is displayed.
[Corrective Action]
Delete the server profile of profile_name, and perform the operation again.
[Description]
Another server profile has been assigned to the server profile_name.
In server_name, the name of the server is displayed.
[Corrective Action]
Delete the server profile configured for the server server_name, and perform the operation again.
[Description]
Failed to delete the server profile.
In server_name, the name of the server is displayed.
In detail, a detailed message is displayed.
[Corrective Action]
Delete the server profile configured for the server server_name, and perform the operation again.
[Description]
The settings for iSCSI boot differ between spare_servers and server_name.
One of the following is displayed in spare_servers and server_name:
L-Server XML
iscsi_user_group_name.rcxprop
iscsi.rcxprop
iSCSI disk resource
When spare_servers or server_name is something other than the above, refer to the explanation in "Message number 61184" in "Messages VE".
[Corrective Action]
Review the settings of spare_servers and server_name, and perform the operation again.
Take corrective action based on the content of spare_servers and server_name.
"L-Server XML"
Review the content of the L-Server XML definition file.
For details on L-Server XML definition files, refer to "Chapter 2 Resource Configuration Information and User Definition Information (XML Files)".
"iscsi_user_group_name.rcxprop" or "iscsi.rcxprop"
Review the content of the iSCSI boot network definition file.
For details on iSCSI boot network definition files, refer to "4.2.4.3 When using an iSCSI LAN for iSCSI Boot" of the "Setup Guide CE".
"iSCSI disk resource"
Review the content of the definition file of the disk used for iSCSI boot.
For details on definition files of disks used for iSCSI boot, refer to "Chapter 2 Resource Configuration Information and User Definition Information (XML Files)".
[Description]
service is not installed.
"DHCP Server" is displayed for service:
[Corrective Action]
After installing service, perform the operation again.
There is also the following case for Resource Orchestrator:
When "DHCP Server" is displayed for service
After installing the standard DHCP service of the OS, perform the operation again.
[Description]
The process function for obj was not executed.
The reason why function was not executed is displayed for detail.
When "failover", "failback", or "recovery" is displayed for function
Due to the reason in detail, the process of failover, failback, or recovery using the rcxstorage command was aborted.
[Corrective Action]
When "failover", "failback", or "recovery" is displayed for function
Collect this message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
The operation is restricted by the license.
[Corrective Action]
SPARC Enterprise servers cannot be registered in environments where Cloud Edition licenses are registered.
[Description]
The version used for the export of the configuration information and the one used for the import are different.
The version used for the export is output in ExportVersion. When the version information does not exist in the configuration information specified at import, "unknown" is output.
The version used for the import is output in ImportVersion.
[Corrective Action]
Use the same version for the export and import system.
[Description]
The format of the specified value, or the content of the XML specified when performing the following is not correct:
Import of Configuration Information
Detailed information is output in the format "message: error part" for detail.
When the message is "invalid MIME type":
The format of the configuration information specified at import is not in XML format.
The specified MIME type is output in the error part.
When the message is "invalid XML tag":
The format of the XML tag information of the configuration information specified at import is not correct.
The XML tag name of the incorrect format is output in the error part.
When the message is "invalid tag name":
An incorrect resource type exists in the configuration information specified at import.
The highest-level tag of the incorrect resource type is output in the error part. When multiple element names are output, they are displayed separated by commas (",").
When the message is "lack of XML tag":
The configuration information specified at import does not contain all of the configuration information required for the resource type.
The highest-level tag of the resource type and the insufficient resource name are output in the error part. When multiple element names are output, they are displayed separated by commas (",").
When the message is "lack of resource tag":
The resource type information of the configuration information specified at import does not contain all of the required resource information.
The highest-level tag of the resource type and the insufficient resource name are output in the error part, separated by commas (",").
When the message is "duplicate XML tag":
There are multiple highest-level tags of the same resource type in the configuration information specified at import. When importing, multiple instances of the same resource type cannot be processed.
The top-level tag of the resource type is output to the error part. When multiple element names are output, they are displayed separated by commas (",").
Import of Network Configuration Information
Detailed information is output in the format "message: error part" for detail.
When the message is "invalid MIME type":
The format of the network configuration information specified at import is not in XML format.
The specified MIME type is output in the error part.
When the message is "invalid XML tag":
The format of the XML tag information of the network configuration information specified at import is not correct.
The XML tag name of the incorrect format is output in the error part.
When the message is "duplicate XML tag":
There are multiple highest-level tags of the same resource type in the network configuration information specified at import. When importing, multiple instances of the same resource type cannot be processed.
The top-level tag of the resource type is output to the error part. When multiple element names are output, they are displayed separated by commas (",").
[Corrective Action]
When Importing Configuration Information
Contact Fujitsu technical staff.
When Importing Network Configuration Information
Perform the operation again after checking the content displayed in detail, and resolving the cause of the error.
For details on the elements and the values, refer to "2.6.1 Creation".
