This section explains the 427XX message series.
[Cloud Edition]
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 and NICnumber used by the virtual network created by the user in advance, are not connected.
The virtual network is not created again, after changing the external connection port specified in the network resource name.
The virtual network is not created again, after changing the physical LAN segment specified in the network resource name.
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.
[Cloud Edition]
Description
The NIC number used by the virtual network is different from the physical LAN segment specified in the network resource name.
Corrective Action
In the following cases, create the virtual network again if necessary.
If you have changed the server NIC definition or the physical LAN segment specified in the network resource name
When the physical LAN segment specified in the network resource name differs from the NIC number used in the virtual network that was created by the user beforehand
[Cloud Edition]
Description
The ports making up the link aggregation lagname of the LAN switch blade switch specified in the network resource have been deleted. Therefore, the L-server using the network resource where the ports making up the link aggregation lagname have been specified may not be able to communicate with other servers.
Corrective Action
Take one of the following actions:
If the released port that makes up the link aggregation is no longer required as an external port for the network resource, change the specifications of the network resource to delete the port from the external ports of the network resource.
If the port was released by mistake, reset the port as part of the link aggregation lagname from the management console of the LAN switch blade switch, then refresh the LAN switch blade switch from the ROR console with the <Update> button to have it recognized by this product.
[Cloud Edition]
Description
An error occurred while executing the script list scriptlist_name, however, the subsequent processes were executed.
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:
"status of device (device_name) is error. line=n"
The status of the network device device_name is error. As the status of another network device for redundancy configuration is valid, the process was continued without executing for the network device device_name.
In device_name, the network device name is displayed.
In n, the line number of the script list scriptlist_name which was not executed is displayed.
"device (device_name) is in maintenance mode. line=n"
The network device device_name is undergoing maintenance. As the status of another network device for redundancy configuration is valid, the process was continued without executing for the network device device_name.
In device_name, the network device name is displayed.
In n, the line number of the script list scriptlist_name which was not executed is displayed.
"deletion of file (file_name) failed"
Deletion of the history information storage area file_name has failed.
In file_name, the name of the file or directory 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.
"status of device (device_name) is error. line=n"
After restoring the status of the network device device_name, log into the network device device_name directly and manually configure the definition, referring to the scriptlist scriptlist_name which was to be executed.
For details on how to log into the network device device_name and delete definitions, refer to the manual for the network device.
"device (device_name) is in maintenance mode. line=n"
Perform the following after maintenance of the network device device_name is complete.
Refer to the script list scriptlist_name that was to be executed, login directly to the network device device_name, and then make the definitions changes manually.
For details on how to log into the network device device_name and delete definitions, refer to the manual for the 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 "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
"deletion of file (file_name) failed"
If the history information storage area file_name exists, delete the history information storage area file_name manually.
This action is not necessary if file_name history information storage area does not exist.
[Cloud Edition]
Description
The execution of script list scriptlist_name was canceled, as an error occurred during the execution.
When this message is output during deletion of an L-Platform, a network resource, or a physical L-Server, operations to release the target resource continue to be executed.
In ruleset_name, the name of the ruleset is displayed.
In scriptlist_name, the script list name is displayed.
In script_name, the name of the script that caused the process to abort or the script name executed after the variable parameter conversion is displayed.
In detail, the following detailed information is displayed:
"unavailable status for auto-config. device=device_name line=n"
The target network device device_name that executes the script script_name specified in the script list scriptlist_name cannot be selected as the target of automatic configuration.
In device_name, the network device name is displayed.
In n, the line number of the script list scriptlist_name which resulted in the aborting of script execution is displayed.
"scripts execution error. device=device_name result=code line=n"
An error occurred while executing the script script_name.
In device_name, the network device name is displayed. When "none" is specified for the node operand in the script list scriptlist_name, a hyphen ("-") is displayed.
In code, the return value of the script in which the error occurred is displayed.
When code is "04"
An error involving failure to connect to the network device device_name or unexpected disconnection from it has occurred.
In other cases
An error other than those above has occurred.
In n, the line number of the script list scriptlist_name at which an error occurred while executing the script is displayed.
"execution timeout. device=device_name line=n"
Timeout of the script monitoring time has occurred during execution of the script list scriptlist_name.
In device_name, the network device name is displayed. When "none" is specified for the node operand in the script list scriptlist_name, a hyphen ("-") is displayed.
In n, the line number of the script list scriptlist_name at which timeout occurred while executing the script is displayed.
"internal error. device=device_name line=n"
An internal error occurred while executing the script list scriptlist_name.
In device_name, the network device name is displayed. When "none" is specified for the node operand in the script list scriptlist_name, a hyphen ("-") is displayed.
In n, the line number of the script list scriptlist_name at which an internal error occurred while executing the script is displayed.
Corrective Action
The tenant administrator or the tenant user should notify the infrastructure administrator of operation details at the time of error occurrence, and the information in this message.
The infrastructure administrator should take the corrective action according to the information displayed in detail.
"unavailable status for auto-config. device=device_name line=n"
If "false" (not the target of auto-configuration) has been set for auto-configuration information for the network device device_name (the AutoConfiguration element) when registering or modifying the network configuration information of the network device device_name
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 "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
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 "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
"scripts execution error. device=device_name result=code line=n"
Identify the cause based on the return value of the script and information in the execution log and take the relevant corrective action.
When executing the script again after performing corrective action, execute the rcxadm netdevice show command to check if the corresponding network device device_name can be selected as a target of auto-configuration. 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 device_name can be selected as a target of auto-configuration.
For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
"execution timeout. device=device_name line=n"
Identify the time-consuming process occurring during execution of the script and take corrective action accordingly.
When the processing time is appropriate, change the "EXECUTE_TIMEOUT" parameter value of script monitoring time in "unm_provisioning.rcxprop".
For details on how to define the script monitoring time, refer to "F.7 Network Device Automatic Configuration and Operation Definition File" in the "Design Guide CE".
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
"internal error. device=device_name line=n"
Collect this message and troubleshooting data, and contact Fujitsu technical staff.
If it is necessary to delete the definition of the network device device_name for which a definition has been configured by the execution of the script, log into the network device device_name directly and delete the definition manually.
For details on how to log into the network device device_name and delete definitions, refer to the manual for the network device.
[Cloud Edition]
Description
As the execution of the script list scriptlist_name was stopped, subsequent scripts were not executed.
For the reason why the execution was stopped, refer to "Message number 42751".
In ruleset_name, the name of the ruleset is displayed.
In scriptlist_name, the script list name is displayed.
In script_name, the name of the script that was not executed or the name of the script that was not executed after conversion of the variable parameter is displayed.
In device_name, the name of the network device for which the script was not executed is displayed. When "none" is specified for the node operand in the script list scriptlist_name, a hyphen ("-") is displayed.
In n, the line number of the script list which was not executed is displayed.
This message is output for each of the scripts which were not executed.
Corrective Action
The tenant administrator or the tenant user should notify the infrastructure administrator of operation details at the time of error occurrence, and the information in this message.
The infrastructure administrator should take the corrective actions for "Message number 42751".
After taking the corrective actions for "Message number 42751", log in to the network device device_name directly and manually delete the definition, referring to the script script_name which was to be executed.
For details on how to log into the network device device_name and delete definitions, refer to the manual for the network device.
[Cloud Edition]
Description
An error occurred while executing the script list scriptlist_name, however, the subsequent processes were executed.
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:
"status of device (device_name) is error. line=n"
The status of the network device device_name is error.
As the status of another network device for redundancy configuration is valid, the process was continued without executing for the network device device_name.
In device_name, the network device name is displayed.
In n, the line number of the script list scriptlist_name which was not executed is displayed.
"device (device_name) is in maintenance mode. line=n"
The network device device_name is undergoing maintenance.
As the status of another network device for redundancy configuration is valid, the process was continued without executing for the network device device_name.
In device_name, the network device name is displayed.
In n, the line number of the script list scriptlist_name which was not executed is displayed.
"deletion of file (file_name) failed"
Deletion of the history information storage area file_name failed, but processing has continued, as the execution of scripts completed successfully.
In file_name, the name of the file or directory of the history information storage area 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.
"status of device (device_name) is error. line=n"
After restoring the status of the network device device_name, request the tenant administrator or the tenant user to perform the operation again.
"device (device_name) is in maintenance mode. line=n"
After performing maintenance tasks on the network device device_name, use the rcxadm netdevice set command to cancel the maintenance mode for device_name, and request the tenant administrator or the tenant user to perform the operation again.
For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
"deletion of file (file_name) failed"
If the history information storage area file_name exists, delete the history information storage area file_name manually.
This action is not necessary if file_name history information storage area does not exist.
[Cloud Edition]
Description
The status of the network device nodeid has changed to status.
Corrective Action
Check the state of the network device.
[Cloud Edition]
Description
The corresponding device is no longer set as the target of auto-configuration, since auto-configuration for the network device target failed.
Corrective Action
Take corrective action for the failure messages of auto-configuration of the network device target displayed before and after this message.
After completing the corrective action, perform modification using the rcxadm netdevice set command so that the network device target can be selected as the target of auto-configuration.
For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".