This section explains the 627XX message series.
[Cloud Edition]
Description
Failed to create the virtual switch name on server server.
When the target server is Hyper-V, replace virtual switch with virtual network.
Corrective Action
Take corrective action based on the content of code.
When code is "15" or "1511"
The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
When using Intel PROSet in Hyper-V, refer to "8.3.10 Advisory Notes for Hyper-V Usage" in the "Setup Guide CE".
When code is "16", "1524", or "1525"
The VM host could not be found.
Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.
If code is "100", "115", "1512", "1526", "1527", "1528", "1529", or "1531"
The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
Check the granted authority using 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 "7.1.7 Changing VM Host Login Account Information" or "7.7 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 "8.3.10 Advisory Notes for Hyper-V Usage" in the "Setup Guide CE".
When 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 operating status and network settings of the VM host or VM management software.
When code is "113" or "1510"
Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software. The login account information may have been changed after the VM host or VM management software was registered.
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 "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If code is "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 "14.3 Network Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When using Intel PROSet in Hyper-V, refer to "8.3.10 Advisory Notes for Hyper-V Usage" in the "Setup Guide CE".
When code is "513"
Failed to create the virtual switch, as the physical network adapter is in use by another virtual switch. Check the network settings of the VM host from VM management software.
When code is "514" or "515"
Communication between the admin server and the VM host/VM management software failed. Check the operating status and network settings of the VM host or VM management software.
When 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 "8.3.10 Advisory Notes for Hyper-V Usage" in the "Setup Guide CE".
When 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 "15.6.1 Creation" in the "Reference Guide (Command/XML) CE".
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.
[Cloud Edition]
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.
When code is "15" or "1511"
The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
When code is "16", "1524", or "1525"
The VM host could not be found.
Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.
When code is "100", "115", or "1512"
The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
Check the granted authority using 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 "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When 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 operating status and network settings of the VM host or VM management software.
When code is "113" or "1510"
Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software. The login account information may have been changed after the VM host or VM management software was registered.
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 "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When code is "520"
Failed to delete the virtual switch. Check the operating status and network settings of the VM host or VM management software. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Resolve the problem with the VM host/VM management software.
When 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.
When code is "523" or "524"
Communication between the admin server and the VM host/VM management software failed. Check the operating status and network settings of the VM host or 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.
[Cloud Edition]
Description
Failed to create the virtual network name on server server.
When the target server is VMware, replace virtual network with the port group on the virtual switch.
Corrective Action
Take corrective action based on the content of code.
When code is "15"
The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
When code is "16"
The VM host could not be found.
Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.
When code is "100" or "115"
The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
Check the granted authority using 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 "7.1.7 Changing VM Host Login Account Information" or "7.7 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 operating status and network settings of the VM host or VM management software.
When code is "113"
Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software. The login account information may have been changed after the VM host or VM management software was registered.
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 "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When 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.
When code is "611"
Failed to create the virtual network. Check the operating status and network settings of the VM host or VM management software. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Resolve the problem with the VM host or VM management software, and then perform the operation.
When 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.
When code is "614" or "615"
Communication between the admin server and the VM host/VM management software failed. Check the operating status and network settings of the VM host or 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.
[Cloud Edition]
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.
When code is "15"
The response from VM host or VM management software to requests from the admin server timed out. Check the operating status and network settings of the VM host or VM management software.
When code is "16"
The VM host could not be found.
Select [Operation]-[Update] from the ROR console menu to update the screen and then check if the VM host has been deleted.
When code is "100" or "115"
The necessary authority may not have been granted in the VM host or VM management software login account information that was registered.
Check the granted authority using 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 "7.1.7 Changing VM Host Login Account Information" or "7.7 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 operating status and network settings of the VM host or VM management software.
When code is "113"
Communication with the VM host or VM management software is not possible using the login account information entered when registering the VM host or VM management software. The login account information may have been changed after the VM host or VM management software was registered.
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 "7.1.7 Changing VM Host Login Account Information" or "7.7 Changing VM Management Software Settings" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When code is "620"
Failed to delete the virtual network. Check the operating status and network settings of the VM host or VM management software. When operation is not possible using VM management software, there is a problem with the VM host or VM management software. Resolve the problem with the VM host/VM management software.
When 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.
When code is "623" or "624"
Communication between the admin server and the VM host/VM management software failed. Check the operating status and network settings of the VM host or 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.
[Cloud Edition]
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 "14.3 Network Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If this message is output during the addition of a NIC or the modification of a connection destination network targeting an L-Server, check that the VM host is not in maintenance mode. When the VM host is in maintenance mode, release it from maintenance mode and then perform the operation again.
[Cloud Edition]
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.
[Cloud Edition]
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.
[Cloud Edition]
Description
There are multiple virtual networks assigned with the same vlanid.
When the target server is VMware, replace virtual network with port group.
The following operations may have been executed.
Using the same vlanid, create a virtual network which has a different virtual network name on VM management software
Create a virtual network which has a different name, but the same vlanid as that of the virtual network which has been automatically configured in Resource Orchestrator
On VM management software, change the virtual network name which has been automatically configured in Resource Orchestrator
On VM management software, change the virtual vlanid which has been automatically configured in Resource Orchestrator
The virtual network name with the same vlanid configured is displayed in detail.
When there are multiple numbers for detail, they are displayed separated by commas (,).
Corrective Action
Configure the virtual network and vlanid combinations so that they are unique in detail.
Use a unique, case-sensitive virtual network name.
When the target server is VMware, 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.1.4 Network Preparations" in the "Design 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.
[Cloud Edition]
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".
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 "15.6.1 Creation" in the "Reference Guide (Command/XML) CE".
[Cloud Edition]
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.
[Cloud Edition]
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.
[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 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.
For a LAN switch blade PY CB Eth Switch 10/40Gb 18/8+2
Confirm the values for Fabric ID, Domain ID, Switch ID which are displayed in the resource details correspond to the values which are configured on the LAN switch blade.
If the values are different, configure LAN switch blade settings corresponding to the values which are displayed in the resource details.
Or, after deleting external ports settings for network resource, update the values which are displayed in resource detail by deleting and registering the LAN switch blades again.
After confirming the values are correct, configure external ports settings of the network resource if necessary.
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.
For a LAN switch blade PY CB Eth Switch 10/40Gb 18/8+2
Use the same procedure as "when server is a physical server".
[Cloud Edition]
Description
The specified configuration is unavailable for automatic network configuration.
Take corrective action based on the content of detail.
Corrective Action
Check the configurations supported for automatic network configuration, and resolve the error.
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 (",").
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 series
CB1 and CB2
CB3 and CB4
CB5 and CB6
CB7 and CB8
When the chassis is a BX600 series
NET1 and NET2
NET3 and NET4
When the chassis is a BX400 series
CB1 and CB2
CB3 and CB4
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.
Create the virtual network on the server server again.
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.
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 series
CB1 and CB2
CB3 and CB4
CB5 and CB6
CB7 and CB8
When the chassis is a BX600 series
NET1 and NET2
NET3 and NET4
When the chassis is a BX400 series
CB1 and CB2
CB3 and CB4
For details, refer to "5.6 Registering Network Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
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.
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 series
CB1 and CB2
CB3 and CB4
CB5 and CB6
CB7 and CB8
When the chassis is a BX600 series
NET1 and NET2
NET3 and NET4
When the chassis is a BX400 series
CB1 and CB2
CB3 and CB4
For details, refer to "5.6 Registering Network Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
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.
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.
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.
Check if the chassis to be used is supported.
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.
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.
For a LAN switch blade PY CB Eth Switch 10/40Gb 18/8+2
Confirm the values for Fabric ID, Domain ID, Switch ID which are displayed in the resource details correspond to the values which are configured on the LAN switch blade.
If the values are different, configure LAN switch blade settings corresponding to the values which are displayed in the resource details.
Or, after deleting external ports settings for network resource, update the values which are displayed in resource detail by deleting and registering the LAN switch blades again.
After confirming the values are correct, configure external ports settings of the network resource if necessary.
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.
Confirm that the port information of individual servers and LAN switch blades is correctly recognized from the server tree in the ROR console.
The VM host vmhost is a VM type which does not support auto-configuration.
Exclude the VM host vmhost from being the target of network auto-configuration, and perform the operation again.
The VM host vmhost is a VM type which supports auto-configuration only when the server type is blade server.
Exclude the VM host vmhost from being the target of network auto-configuration, and perform the operation again.
The auto attribute for the specified network resource is "false".
When performing auto-configuration, specify "true" for the auto attribute during network resource creation.
A combination other than CB1 and CB2, CB3 and CB4, CB5 and CB6, or CB7 and CB8 has been mounted as the configuration element of the external connection ports on the LAN switch blade specified for the network resource.
In exdetail, the following is displayed:
port=(External_connection_port,LAN_switch_blade_name or Ethernet_Fabric_switch_name)[/(...,...)],vmhost=Destination_VM_host_name,chassis=Chassis_name
When an external connection port of an Ethernet Fabric switch or LAN switch blade is specified, the LAN switch blade combinations which support VLAN auto-configuration for internal connection ports, as configuration elements of LAN switch blades in the Ethernet Fabric, are CB1 and CB2, CB3 and CB4, CB5 and CB6, and CB7 and CB8. To use a combination other than those, define the physical NIC configuration in the server NIC definition file.
Or, review the specified locations of the external connection ports.
For details on server NIC definitions, refer to "15.13 Server NIC Definition" in the "Reference Guide (Command/XML) CE".
An external connection port has not been specified for the network resource.
When using an Ethernet Fabric switch, specify the external connection port.
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 "15.6.1 Creation" in the "Reference Guide (Command/XML) CE".
[Virtual Edition]
Description
Processing was stopped, as errors were detected in the values specified in the definition file displayed in filename.
When filename is "sparc_vm.rcxprop"
There is an error in a value specified in the definition file for enabling Solaris Zones.
Corrective Action
When filename is "sparc_vm.rcxprop"
There is an error in the specified value displayed in item. Review the specified values, correct the definition, and then perform the operation again.
[Cloud Edition]
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.
When filename is "sparc_vm.rcxprop"
There is an error in a value specified in the definition file for enabling Solaris Zones.
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 "8.1.6 Definition File for Alive Monitoring" in the "Setup Guide CE".
When filename is "sparc_vm.rcxprop"
There is an error in the specified value displayed in item. Review the specified values, correct the definition, and then perform the operation again.
[Cloud Edition]
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 "15.13 Server NIC Definition" in the "Reference Guide (Command/XML) CE".
[Cloud Edition]
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.
[Cloud Edition]
Description
The creation of a virtual switch connecting to NIC(number) using the network resource name on the server server failed. When the target server is Hyper-V, replace virtual switch with virtual network.
The NIC index number configured for the virtual switches for which creation failed is displayed in number. When there are multiple numbers for number, they are displayed separated by commas (,).
The NIC index number indicates the following:
When using blade servers
The physical link information Index displayed by selecting the [Resource Details] tab of the server attributes on the server tree.
When using rack mount servers or tower servers
The index corresponding to the NIC name which can be recognized by the server virtualization software.
When using VMware, the index number is an integer starting from 1, corresponding to the NIC name of the managed server (vmnic0,vmnic1,vmnic2...), which can be recognized by VMware.
The following detailed information is given in detail.
"specified NIC is connected to another virtual switch"
The target NICs are connected to different virtual switches.
"some specified NICs are unable to connect to the virtual switch"
Some of the target NICs cannot be connected with virtual switches.
"extra NIC is connected to virtual switch"
NICs other than the target NICs are connected to the target virtual switches.
"failed to connect NIC to virtual switch"
The connection of the target NICs to virtual switches failed.
The target NICs indicate the following:
When specifying physical LAN segments for network resources
NICs specified in the server NIC definitions
When not specifying physical LAN segments for network resources
NIC combinations that are supported by automatic network configuration in Resource Orchestrator
Corrective Action
From the VM management software, check the connection status between the physical network adapter and the virtual switch of the VM host.
For details on the settings, refer to "8.2.4 Automatic Network Configuration" and "8.2.5 Manual Network Configuration" in the "Setup Guide CE", or "8.3.4 Automatic Network Configuration" and "8.3.5 Manual Network Configuration" in the "Setup Guide CE".
When using a physical LAN segment, check the NIC index of the server NIC definition corresponding to the physical LAN segment specified for the network settings and network resources of the VM host.
[Cloud Edition]
Description
Operation of the port profile of the Ethernet fabric switch failed.
In device_name, the name of the Ethernet Fabric switch is displayed.
In port_profile_name, the name of the port profile is displayed.
In operation, one of the following is displayed:
creation
deletion
association
disassociation from vsiid
In vsiid, the vsiid of the L-Server is displayed.
replacing
In cause, one of the following causes is displayed:
"login failed"
The Ethernet fabric cannot be logged in to.
"the number of port profiles exceeds the limit"
The number of port profiles on the Ethernet Fabric switch has reached the upper limit.
"the number of associations exceeds the limit"
The number of port profiles on the Ethernet Fabric switch has reached the upper limit.
"port profile not found"
The port profile was not found on the Ethernet Fabric switch.
"vfab(vfab name) not found in Ethernet Fabric switch name"
vfab name does not exist on Converged Fabric (Ethernet Fabric switch name).
"failed to control the fabric"
Control of the Ethernet Fabric switch failed.
Corrective Action
Take corrective action based on the content displayed for cause.
When cause is "login failed"
Check the following and perform the last operation again.
Confirm that a communication route from the ROR manager to the Ethernet fabric switch has been secured.
Execute the rcxadm netdevice show -name name command for the Ethernet Fabric switch and confirm that the information (login name, password) for connecting with the Ethernet Fabric is correct.
If operation is "deletion", the process will be continued after the message is output.
Manually delete the port profile of the Ethernet Fabric switch if necessary.
If operation is "disassociation from vsiid", the process will be continued after the message is output.
If necessary, manually delete the link between the VSIID indicated by vsiid and the port profile of the Ethernet Fabric switch.
When cause is "the number of port profiles exceeds the limit"
Confirm the configuration of the Ethernet Fabric and delete any network resources that are not being used or perform other modifications necessary to make it possible to create a new port profile on the port profile of the Ethernet fabric switch.
When cause is "the number of associations exceeds the limit"
Confirm the configuration of the Ethernet Fabric and delete any links between port profiles and MAC addresses that are not being used or perform other modifications necessary to make it possible to create a new link between a port profile and a MAC address on the Ethernet Fabric switch.
When cause is "port profile not found"
Confirm that the port profile already created using Resource Orchestrator or the port profile defined in the definition file for linking network resources with port profiles exists on the Ethernet Fabric switch, and then perform the last operation again.
When cause is "vfab(vfab name) not found in Ethernet Fabric switch name"
Check that vfab name exists on the Converged Fabric (Ethernet fabric switch name), and then perform the last operation again.
When cause is "failed to control the fabric"
Manual configuration and operation from Resource Orchestrator may have been performed on the Ethernet Fabric switch at the same time.
Perform the last operation again from Resource Orchestrator.
[Cloud Edition]
Description
As the tenants to which operation target resources belong are different, the operations have not been executed.
The name of the resource which the operation was not performed is displayed in detail.
When there are multiple resources, they are displayed separated by commas (,).
Corrective Action
Perform the operation again after moving the resources displayed in detail to the same tenant.
[Cloud Edition]
Description
VFAB auto-configuration of Converged Fabric failed.
In device_name, the network device name of Converged Fabric is displayed.
In vfab_ids, the VFAB ID is displayed. When multiple items are displayed, they are displayed separated by commas (,).
In operation, one of the following is displayed:
Addition
Deletion
Modification
Configuration
In detail, the following detailed information is displayed:
"specified VFAB has already set"
The target VFAB has already been pre-configured.
"login failed"
Unable to log in to Converged Fabric.
"number of ifgroups exceeds the limit"
The number of the interface group has reached the upper limit in Converged Fabric.
"port profile not found"
The port profile cannot be found in Converged Fabric.
"VFAB(vfab name) not found in Network device name"
vfab name does not exist on Converged Fabric (Network device name).
"VFAB(vfab name) is mode mode in Network device name"
Operations failed, since the VFAB (vfab name) on Converged Fabric (Network device name) is in mode mode.
"port(port) not found"
The port specified for "Dot1adPort" or "CirPort" in the network configuration information (XML definition) was not found.
In port, the port name of Converged Fabric is displayed.
"lag(lagname) not found"
The link aggregation group of the CIR specified for "CirPort" in the network configuration information (XML definition) was not found.
In lagname, the link aggregation group name of Converged Fabric is displayed.
"failed to control the fabric"
Control of Converged Fabric failed.
"failed to activate dot1ad mode.port=port"
Failed to activate dot1ad mode for port.
In port, the port name of Converged Fabric is displayed.
"port(port) is a member of link aggregation"
In port, the member port name of the link aggregation is displayed.
Corrective Action
Take corrective action based on the content of detail
"specified VFAB has already set"
Check the following items for the target VFAB, and perform the operation again.
vfab use has not been executed, and
vfab cir-ports has not been executed, and
vfab mode has not been executed, and
The vfab dot1ad ifgroup command has not been executed, and
The status of the port in dot1ad mode used for the relevant VFAB is either of the following:
The port does not belong to the interface group of Converged Fabric
The port only belongs to the interface group of Converged Fabric, which consists only of ports in dot1ad mode. There are no VLANs configured in the interface group.
"login failed"
Check the following and perform the last operation again.
Confirm that a communication route from the ROR manager to Converged Fabric has been secured.
Execute the rcxadm netdevice show -name name command for Converged Fabric and confirm that the information (login name, password) for connection is correct.
"number of ifgroups exceeds the limit"
Check the Converged Fabric settings, and delete the unused ifgroup or perform other operation to enable creation of the interface group on Converged Fabric.
"VFAB(vfab name) not found in Network device name"
Check that the VFAB vfab name exists on the Converged Fabric (Network device name), and then perform the last operation again.
"VFAB(vfab name) is mode mode in Network device name"
Check the mode of the target VFAB in Converged Fabric and perform the last operation again.
"port(port) not found"
Review the port name specified in the network configuration information (XML definition), and then perform the last operation again.
"lag(lagname) not found"
Review the link aggregation group name specified in the network configuration information (XML definition), and then perform the last operation again.
"failed to control the fabric"
Manual configuration and operation from Resource Orchestrator may have been performed on Converged Fabric at the same time.
Perform the last operation again from Resource Orchestrator.
"failed to activate dot1ad mode.port=port"
The VLAN for the interface group to which port belongs has been configured.
Check the VLAN settings of the interface group.
"port(port) is a member of link aggregation"
When the port specified in port is the member port of the link aggregation group, specify the link aggregation group name for CirPort in the network configuration information (XML definition).
[Cloud Edition]
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 "F.3 Creating a Folder for Registering Rulesets" in the "Design Guide CE".
"not found"
When this error is output while operating an L-Platform
Specify the same ruleset names as specified when operating an L-Platform and specified for the corresponding ruleset parameter file (default_param.prm).
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.
When this error is output during execution of the rcxadm slb command
Change the ruleset name specified for "-ruleset" to the correct ruleset name. Specify the same ruleset names as specified for "-ruleset" and specified for the corresponding ruleset parameter file (default_param.prm).
"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 ("_").
[Cloud Edition]
Description
One of the following files contains an error:
Parameter file
The file storing the information from when an L-Platform including a firewall or a server load balancer 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 or a server load balancer 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 or a server load balancer 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
The file storing the information from when an L-Platform including a firewall or a server load balancer 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
The file storing the information from when an L-Platform including a firewall or a server load balancer 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.
Create the file filename, if there is no file filename.
When access privileges for the directory to register the ruleset ruleset_name, for the directory to deploy the interface configuration file to, and for the files under their respective directories have not been granted, grant the privileges.
If the hard disk is full, secure more disk space.
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.
When access privileges for the files in the directory (including its child directories) to register the ruleset ruleset_name have not been granted, grant the privileges.
If the hard disk is full, secure more disk space.
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.
[Cloud Edition]
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"
The script list scriptlist_name is not a text file.
"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.
[Cloud Edition]
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 rulesets 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.
For the scripts that have been grouped with the same number in the script list scriptlist_name, the network device name specified in the node operand has been duplicated.
If there are more than one script group that has been grouped with the same number in the script list scriptlist_name, the specification of node operand does not match.
When operand_name is "node"
A node operand has not been specified.
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 rulesets 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.
If the network device name specified in the node operand has been duplicated in the scripts that have been grouped with the same number in the script list scriptlist_name, remove the duplicate specification of the network device name in the node operand.
If there are more than one script that has been grouped with the same number in the script list scriptlist_name, when the node operand specification status is not the same, configure the same status regarding the presence or lack of the node operand.
When operand_name is "node"
When a node operand has not been specified, specify a node operand.
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.
[Cloud Edition]
Description
The descriptions in the script list scriptlist_name do not match the descriptions specified in the ruleset for a firewall or server load balancer used when creating an L-Platform.
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:
"device name.line=n"
The names of the following network devices are not the same:
The network device name specified in the create script list
The network device name specified in the script list scriptlist_name.
In n, the line number of the script list at which an error occurred is displayed.
When n is "0", the specification of the node option, and the specification details for the same scripts are different in the script list scriptlist_name and the create script list
"group device. line=n"
The number of the following network devices are not the same:
The number of network devices to execute the grouped scripts with the same group number in create.lst
The number of the network devices to execute scripts that have been grouped 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 create.lst
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 create.lst 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.lst 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 create.lst 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.
"device name.line=n"
When scriptlist_name is modify.lst
Correct the network device name specified in the script list scriptlist_name, so that it is the same as the one specified in the create script list, or specify "none".
When scriptlist_name is delete.lst
Correct the network device name specified in the script list scriptlist_name, so that it is the same as the one specified in the create script list.
"group device. line=n"
Correct the number of the network devices to execute 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 create.lst.
"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 create.lst.
"script path. line=n"
Correct the script path specified in the script list scriptlist_name so that it matches the script path specified in create.lst.
[Cloud Edition]
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 (The file name with a serial number may be displayed)
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 (The file name with a serial number may be displayed)
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.
When access privileges for the files in the directory to register the ruleset ruleset_name have not been granted, grant the privileges.
If the hard disk is full, secure more disk space.
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.
[Cloud Edition]
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:
A network device that can be selected for automatic setting does not exist in the network pool.
When performing automatic configuration and operation of a network device in user customization mode, a network device which satisfies all of the following conditions in the network pool is not registered.
The vendor name of the script storage folder specified in the script list scriptlist_name matches the vendor name of the network device.
The model name or the device name of the script storage folder specified in the script list scriptlist_name matches the model name or the vendor name of the network device.
The type of the network device of the ruleset ruleset_name can be automatically configured, and matches the type of the network device which can also be automatically configured.
A network device configuration (redundant/non-redundant) specified in the script list scriptlist_name matches the network device configuration (redundant/non-redundant).
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 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:
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 maintenance mode (maintenance) of the network device is "ON" and the operational status (Status) is "error"
Take corrective action according to "9.5.1.5 Maintenance Procedure of Network Devices Placed into Maintenance Mode due to Failure of Automatic Configuration" in the "Operation Guide CE" and perform the operation again.
If the maintenance mode (maintenance) of the network device is "ON" and the operational status (Status) is something other than "error"
Retry after the maintenance tasks on the network device are complete.
If the operational status (Status) of the network device is something other than "normal" or "error"
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 automatic setting selectability status (AutoConfiguration) of the network device is "false"
Set "true" for the automatic configuration setting (the AutoConfiguration element) of the corresponding network device device_name in the network configuration information, then modify it using the rcxadm netdevice modify command.
For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
When performing automatic configuration and operation of a network device in user customization mode, register a network device which satisfies all of the following conditions in the network pool.
The vendor name of the script storage folder specified in the script list scriptlist_name matches the vendor name of the network device.
The model name or the device name of the script storage folder specified in the script list scriptlist_name matches the model name or the vendor name of the network device.
The type of the network device of the ruleset ruleset_name can be automatically configured, and matches the type of the network device which can also be automatically configured.
A network device configuration (redundant/non-redundant) specified in the script list scriptlist_name matches the network device configuration (redundant/non-redundant).
If one is already registered, check the redundancy configuration (group ID of network configuration information).
For details of network configuration information, refer to "15.7 Network Configuration Information" in the "Reference Guide (Command/XML) CE".
When the network device name is specified for the node operand in the script list scriptlist_name, perform the following:
If the configurations (redundant/non-redundant) of the specified network devices device_name are not the same, register a network device with the same configuration.
When the specified network device device_name is "IPCOM VA", and the S-TAG of the network device and the S-TAG of the virtual fabric corresponding to the tenant to which the network pool belong are different, register the network device using the same S-TAG.
When the vendor name of the specified network device device_name does not match the vendor name of the script storage folder specified in the script list scriptlist_name, register the network devices with matching vendor names.
When the model name or device name specified in the network device device_name does not match the model name or device name of the script storage folder specified in the script list scriptlist_name, register a network device which has a matching model name or device name.
"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.
[Cloud Edition]
Description
There is an error in the status of the network device device_name used when 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 which executes the scripts specified in the script list scriptlist_name is not in the normal state.
"maintenance mode"
The network device device_name which executes 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 corrective action according to the information displayed in status.
"error"
Check the status of the network device device_name which executes the scripts specified in the script list scriptlist_name, and remove the cause of errors.
"maintenance mode"
If "Message number 42783" was output before this message
Take corrective action according to "9.5.1.5 Maintenance Procedure of Network Devices Placed into Maintenance Mode due to Failure of Automatic Configuration" in the "Operation Guide CE".
In other cases
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 "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
"unavailable for auto-config"
If "Message number 42783" was output before this message
Take corrective action according to "9.5.1.5 Maintenance Procedure of Network Devices Placed into Maintenance Mode due to Failure of Automatic Configuration" in the "Operation Guide CE".
In other cases
Set "true" for the automatic configuration setting (the AutoConfiguration element) of the corresponding network device device_name in the network configuration information, then modify it using the rcxadm netdevice modify command.
For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
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.
[Cloud Edition]
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.
[Cloud Edition]
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 "3.7 rcxadm netconfig" in the "Reference Guide (Command/XML) CE".
For details of network configuration information, refer to "15.7 Network Configuration Information" in the "Reference Guide (Command/XML) CE".
[Cloud Edition]
Description
The execution of the script list scriptlist_name was canceled, as an error occurred during execution.
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. 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 is displayed.
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 is displayed.
Detailed information may be displayed when there is incorrect network configuration information.
"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.
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=code line=n" and code is something other than 08
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 "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
For details of network configuration information, refer to "15.7 Network Configuration Information" in the "Reference Guide (Command/XML) CE".
If this message is output when operating an L-Platform, check if there is an error in the following files:
[Windows]
Installation_folder\SVROR\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 "15.17 Network Device Interface Configuration File" in the "Reference Guide (Command/XML) CE".
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"
The scripts specified in the script list scriptlist_name use SSH for connection to the network device device_name. Also, when code is "01"
Check if the library decided in the script specifications is stored in the location specified in the specifications.
In the following cases, for details on the SSH libraries to use and the library storage location, refer to "F.2.1 When Connecting to Network Devices with SSH" in the "Design Guide CE".
When using a sample script to perform SSH connections
When the specifications of the SSH library to use and its storage location are the same as the specifications of the sample scripts
In other cases
Perform the following corrective actions:
Check the network device and the communication path to the network device.
When a problem is found, remove the cause of the problem.
Check that pre-configuration necessary for the network device has been performed.
If necessary, login to the network device and manually perform configuration.
Check the definition of the network device which was configured by execution of the script.
If deletion of the definition is necessary, login to the network device and manually perform configuration.
For details on the procedure to log in to a network device and perform configuration, 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 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 Files" in the "Design Guide CE".
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.
Check if maintenance mode has been configured on the network device device_name. If maintenance mode is configured, take corrective action for the corresponding network device according to "9.5.1.5 Maintenance Procedure of Network Devices Placed into Maintenance Mode due to Failure of Automatic Configuration" in the "Operation Guide CE" and release maintenance mode.
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 "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
[Cloud Edition]
Description
Parsing of the file filename has failed.
Parameter filename, interface configuration file, or unm_provisioning.rcxprop is displayed for filename.
In ruleset_name, the name of the ruleset is displayed.
In scriptlist_name, the script list name is displayed. When there is no information, a hyphen ("-") is displayed.
In detail, the following detailed information is displayed:
"impossible analyze as XML format"
filename has not been specified in the correct XML format.
"not found item (item_name)"
item_name is not defined in file filename.
When there are two or more items, they are displayed separated by commas (,).
"invalid value item=item_name value=value"
The value specified for the item_name in file filename is invalid.
When there are two or more items, they are displayed separated by commas (,).
"duplicate item (item_name)"
Duplicate item_name items are specified in file filename.
When there are two or more items, they are displayed separated by commas (,).
"not found value item=item_name"
The value is not set for item_name in file filename.
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.
"impossible analyze as XML format"
Correct filename so that it can be read as an XML file.
"not found item (item_name)"
Correctly set the item_name in the file filename.
"invalid value item=item_name value=value"
Correct the value value of item_name in the file filename.
"duplicate item (item_name)"
Delete any duplicate definitions of item_name in the file filename.
"not found value item=item_name"
Set the value of item_name in the file filename.
[Cloud Edition]
Description
Creation of the file or directory obj failed during the execution of script defined in the script list scriptlist_name.
The name of the file or directory for information storage created when executing the scripts is displayed in obj.
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 operation details at the time of error occurrence, and the information in this message.
The infrastructure administrator should check the following and resolve the cause of the error.
When the length of the file path specified in the nth line of the script list scriptlist_name is near the OS limit, make the file name shorter.
When access privileges for the files or the directories obj have not been granted, grant the privileges.
If the hard disk is full, secure more disk space.
[Cloud Edition]
Description
Access to the file obj failed during the execution of the script defined in the script list scriptlist_name.
In obj, the name of the file of information storage created when executing the scripts 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 operation details at the time of error occurrence, and the information in this message.
Then the infrastructure administrator should check the following and perform any necessary corrective action.
When access privileges for the file obj and the directory where the file obj exists have not been granted, grant the privileges.
If the hard disk is full, secure more disk space.
[Cloud Edition]
Description
Operation logs output by the execution of the ruleset ruleset_name for operations cannot be obtained.
In ruleset_name, the name of the ruleset is displayed.
Corrective Action
Execute the operation again.
When the same errors are displayed, notify the infrastructure administrator of the information in this message.
An infrastructure administrator should collect this message and troubleshooting data, and contact Fujitsu technical staff.
[Cloud Edition]
Description
The results of operations output by the execution of the script list scriptlist_name exceeded the upper limit of the result of the operational rulesets (500 KB by default).
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 operation details at the time of error occurrence, and the information in this message.
The infrastructure administrator must perform the following corrective action:
When using auto-configuration and operations for the network device using user customization mode
Review the amount of operations (number of commands, command parameters) performed at one time, and change the value of the results of operations output by the execution of script list to a value below the upper limit of the result of the operational rulesets.
Change the "SCRIPT_OUTPUT_SIZE_LIMIT" parameter value, which is the upper limit output value in "unm_provisioning.rcxprop" for the execution results of operation rulesets.
For details on how to define the upper limit of the execution results of rulesets for operations, refer to "F.7 Network Device Automatic Configuration and Operation Definition Files" in the "Design Guide CE".
[Cloud Edition]
Description
The execution of the script list scriptlist_name was canceled, as an error occurred during execution.
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:
"script returned error code. 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. 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 is displayed.
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 is displayed.
"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.
Corrective Action
When the following conditions are met, the tenant administrator or tenant user should execute the following corrective actions:
When detail is "script returned error code. device=device_name result=code line=n", and code is something other than 08
When the message is output during execution of operations, check the usage conditions (prerequisite L-Platform settings or operations) for rulesets described in the explanation of the ruleset ruleset_name.
When the usage conditions of the ruleset are not described in the ruleset ruleset_name explanation, check with the infrastructure administrator.
After clearing the usage conditions necessary for rulesets during operations, perform the operation again.
For anything other than the above, perform the operation again.
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 take the corrective action according to the information displayed in detail.
"script returned error code. device=device_name result=code line=n"
When device_name is a hyphen ("-"), and code is "08"
If the scripts specified in the nth line in the script list scriptlist_name are the following, check the status of the network device, and take corrective action.
When using sample scripts
Same as sample scripts, when the specifications have been customized so the operation result is displayed in the last line.
When the network device is in a redundancy configuration, or only one device is configured in maintenance mode, check if the standby network device has not been configured in maintenance mode.
When maintenance mode is configured, set maintenance mode for the standby network device.
For details on how to configure maintenance mode, refer to "22.1 Switchover of Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When the case is something other than the above or the detailed status confirmation results do not match the conditions
Check the network device and the communication path to the network device, and then remove the cause of the error.
"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 Files" in the "Design Guide CE".
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.
Check if maintenance mode has been configured on the network device device_name. If maintenance mode is configured, take corrective action for the corresponding network device according to "9.5.1.5 Maintenance Procedure of Network Devices Placed into Maintenance Mode due to Failure of Automatic Configuration" in the "Operation Guide CE" and release maintenance mode.
[Cloud Edition]
Description
A selectable network device cannot be found.
In detail, the following detailed information is displayed:
"cannot connect network resources. network_resources=network_resources ruleset=ruleset_name scriptlist=script_list line=n"
From the selectable network device, communication with the network resource network_resources is not possible.
In network_resources, the network resource to be used when creating an L-Platform is displayed.
When there are multiple network resources, they are displayed separated by commas (,).
In ruleset_name, the name of the ruleset is displayed.
In script_list, the script list name is displayed.
In n, the line number of the script list 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 resolve the cause of the error based on the content displayed in detail.
"cannot connect network resources. network_resources=network_resources ruleset=ruleset_name scriptlist=script_list line=n"
Check the usage status of the network resource network_resources for each network device, and review the network design and the ruleset so that a single network resource is not used by multiple network devices.
Use the rcxadm firewall list -extend network command to check the usage status.
For details on the rcxadm firewall command, refer to "3.4 rcxadm firewall" in the "Reference Guide (Command/XML) CE".
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 maintenance mode (maintenance) of the network device is "ON" and the operational status (Status) is "error"
Take corrective action according to "9.5.1.5 Maintenance Procedure of Network Devices Placed into Maintenance Mode due to Failure of Automatic Configuration" in the "Operation Guide CE" and perform the operation again.
If the maintenance mode (maintenance) of the network device is "ON" and the operational status (Status) is something other than "error"
Retry after the maintenance tasks on the network device are complete.
If the operational status (Status) of the network device is something other than "normal" or "error"
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 automatic setting selectability status (AutoConfiguration) of the network device is "false"
Set "true" for the automatic configuration setting (the AutoConfiguration element) of the corresponding network device in the network configuration information, then modify it using the rcxadm netdevice modify command.
For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
[Cloud Edition]
Description
The network resource network_resource of the operation targets are used in the firewall or a server load balancer that is deployed in the L-Platform.
Corrective Action
Remove the cause of the error using the following procedure:
Check the usage status of the network resource network_resource of the operation target.
Use the rcxadm firewall list -extend network command to check the usage status in the firewall.
Use the rcxadm slb list -extend network command to check the usage status in the server load balancer.
After canceling all L-Platforms in which firewalls or server load balancers using the network resources network_resource of the operation targets are deployed, perform the operation again.
[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:
"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. 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 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 is displayed.
Detailed information may be displayed when there is incorrect network configuration information.
Corrective Action
When the following condition is met, the tenant administrator or tenant user should execute the operation again:
When detail is "scripts execution error. device=device_name result=code line=n" and code is something other than 8
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 and
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 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 "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
For details of network configuration information, refer to "15.7 Network Configuration Information" in the "Reference Guide (Command/XML) CE".
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 "15.17 Network Device Interface Configuration File" in the "Reference Guide (Command/XML) CE".
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"
The scripts specified in the script list scriptlist_name use SSH for connection to the network device device_name. Also, when code is "1"
Check if the library decided in the script specifications is stored in the location specified in the specifications.
In the following cases, for details on the SSH libraries to use and the library storage location, refer to "F.2.1 When Connecting to Network Devices with SSH" in the "Design Guide CE".
When using a sample script to perform SSH connections
When the specifications of the SSH library to use and its storage location are the same as the specifications of the sample scripts
In other cases
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.
If detail is "scripts execution error. device=device_name result=code line=n", and code is 8, take corrective action for the corresponding network device according to "9.5.1.5 Maintenance Procedure of Network Devices Placed into Maintenance Mode due to Failure of Automatic Configuration" in the "Operation Guide CE" and release maintenance mode.
[Cloud Edition]
Description
In device_name, the network device name is displayed.
In serial_number_per_device, the serial numbers for each network device are displayed.
One of the following network device statuses is displayed in status:
"error"
The status of the target network device device_name is not normal.
"maintenance mode"
The target network device device_name is undergoing maintenance.
"unavailable for auto-config"
The target network device device_name is unavailable for automatic configuration because execution of the script 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 corrective action according to the information displayed in status.
"error"
Check the status of the target network device device_name, and resolve the cause of the error.
"maintenance mode"
For cases other than adove
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 "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
"unavailable for auto-config"
If "Message number 42783" was output before this message
Notify Fujitsu technical staff of the operations to be performed and the content of this message.
In other cases
Set "true" for the automatic configuration setting (the AutoConfiguration element) of the corresponding network device device_name in the network configuration information, then modify it using the rcxadm netdevice modify command.
For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
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.
"NETCONF unreachable"
The network device does not respond to NETCONF monitoring of status.
"auto configuration failed"
Auto-configuration for the network device failed.
Corrective Action
Check the state of the network device nodeid.
Identify the cause based on the content displayed in cause and resolve the 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.
"NETCONF unreachable"
Identify the cause that prevents the network device from responding to NETCONF 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.
"auto configuration failed"
Before or after this message was output, script execution on the network device nodeid or script execution on the network device which configures a redundant configuration with the corresponding network device nodeid failed, as notified by the following messages:
"Message number 42750"
"Message number 42751"
"Message number 62760"
"Message number 62766"
"Message number 62770"
"Message number 67999"
Based on the message that was output, identify the cause of the script execution error on the network device and resolve the cause of the error.
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 Virtual Edition, for details on the vendor names and device names of network devices, refer to "7.7 When Managing Network Devices as Resources" in the "Design Guide VE".
For Cloud Edition, for details on the vendor names and device names of network devices, refer to "9.4.8 When Managing Network Devices as Resources" in the "Design 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.
[Cloud Edition]
Description
The network device file management function is disabled.
CONFIG_BACKUP of unm_mon.rcxprop is "false".
Corrective Action
Check the detailed configurations of unm_mon.rcxprop.
For details on how to define the detailed configurations, refer to "9.4.8.2 When Using the Network Device File Management Function" in the "Design Guide CE".
[Cloud Edition]
Description
An error occurred in a network device, so network device file operations failed.
In device_name, the target network device name is displayed.
In status, the status of target network device 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 must check the status of network device device_name, and resolve the cause of errors.
[Cloud Edition]
Description
As the backed up network device files no longer exist, restoration of the network device configuration files failed.
In device_name, the target network device name is displayed.
In file_type, when the network device configuration file has been specified, "network device configuration file" is displayed, and the network device environment file has been specified, "network device environment file" is displayed.
Corrective Action
Check if the values specified for -name or -type of the rcxadm netdevice cfbackup command are correct.
For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
[Cloud Edition]
Description
Operation (backup or restoration) of a network device file has failed.
In device_name, the target network device name is displayed.
In operate, "backup" or "restore" is displayed according to the executed operation.
In code, the following cause codes are displayed.
When code is "04"
A mistake in registration information or a problem for which the operation can be performed again, such as a connection error or timeout detection, has occurred.
In Other Cases
An error (other than that above) for which the operation cannot be performed again has occurred.
Corrective Action
When code is "04"
When executing the rcxadm netdevice command
Confirm the login information and the external server information registered using the network configuration information.
When there are mistakes, execute the same command after correcting the login information or external server information for the corresponding network device.
When there are no errors, wait a while, and execute the same command again.
In other cases (operations such as backup when creating an L-Platform)
Confirm the login information and the external server information registered using the network configuration information.
When there are mistakes, execute the rcxadm netdevice cfbackup command after correcting the login information and the external server information of the corresponding network device.
When there are no mistakes, wait a while, and execute the rcxadm netdevice cfbackup command.
In cases other than the above, or when the problem persists even after re-execution
Notify the infrastructure administrator of the operations to be performed and the information of this message.
The infrastructure administrator should check for the following mistakes.
Check the network device and the communication path to the network device, and then remove the cause of the error.
Check if there are mistakes in preparations to use the network device file management function, and the correct any mistakes.
If a file which is not allowed to be created in the devices as described in the Advisory Notes in Preparations has been created, delete it.
For details on preparations to use the network device file management function, refer to "9.4.8.2 When Using the Network Device File Management Function" in the "Design Guide CE".
When performing restoration operations, check that the definitions of the network device file for the restoration target and the network device settings are not contradictory.
Use the rcxadm netdevice cfexport command to obtain the network device file for the restoration target.
For details on the rcxadm netdevice command, refer to "3.8 rcxadm netdevice" in the "Reference Guide (Command/XML) CE".
Directly log in to the network device for which the definition settings have been configured to check the details.
For details on how to log into a network device and how to check the settings, refer to the manual for the network device.
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Cloud Edition]
Description
key for obj1 is used for obj2.
[KVM]
When obj1 and obj2 are the cloning image name (image location type), and when key is "name"
When collecting cloning images, the specified image name (obj1) is used for obj2.
Corrective Action
[KVM]
When obj1 and obj2 is the cloning image name (image location type), and when key is "name"
A cloning image with the same name cannot be collected in the same image pool.
Perform the operation again after specifying a different image name.
For details, refer to "Collecting Cloning Images from L-Servers with an OS Installed" in "17.5.1 Collecting and Registering" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Description
Release from maintenance mode cannot be performed because an error occurred during communication with the network device device.
One of the following is displayed in detail:
"Ping unreachable"
The network device device is not responding to the PING for alive monitoring.
"SNMP unreachable"
The network device device does not respond to SNMP monitoring of status.
"NETCONF unreachable"
The network device device does not respond to NETCONF monitoring of status.
"Timeout"
A timeout has occurred during communication with the network device device.
Corrective Action
Identify and resolve the problem based on the content displayed in detail.
"Ping unreachable"
Identify and resolve the problem that prevents the network device device from responding to PING.
If there is no problem in the network device 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 and resolve the problem that prevents the network device device from responding to SNMP.
If there is no problem in the network device 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.
"NETCONF unreachable"
Identify and resolve the problem that prevents the network device device from responding to NETCONF.
If there is no problem in the network device 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.
"Timeout"
Perform the operation again.
If the problem persists even after performing the operation again, collect troubleshooting information and contact Fujitsu technical staff.
Description
Setting of the network configuration information for the network device device has failed due to the cause displayed in detail.
In configuration, the element name of the network configuration information is displayed.
One of the following is displayed in detail:
"status is error"
configuration cannot be changed because the status of the network device device is "error".
"monitoring method error"
configuration cannot be specified because the monitoring method specified for the network device device, is not supported.
Corrective Action
Identify and resolve the problem based on the content displayed in detail.
"status is error"
Referring to the message in "Message number 62780" output for the network device device, take corrective action for the cause of the "error" status of the network device.
"monitoring method error"
Specify a monitoring method which supports the network device device, and then try again.
Monitoring method specifiable for VCS
ping
NETCONF
Monitoring method specifiable for non-VCS
ping
SNMP
Description
The network device device cannot be managed as the resource type type.
In device, the name of the managed network device or its admin IP address is displayed.
This error may occur during the following conditions:
An incorrect resource type was specified when registering the network device
The managed network device was replaced with a different model of device during operation
Corrective Action
When this message was output during registration of the network device
Check the following: If there is an error in the XML, correct it and execute the same command again.
Check whether the admin IP address specified as the ip attribute of the Netdevice element is correct.
Check if the value specified for the Type element is correct.
The values which can be specified for elements differ depending on the type of network device.
For Virtual Edition, for details, refer to "7.5 Registering Network Devices" in the "User's Guide VE".
For Cloud Edition, for details, refer to "5.7 Registering Network Devices" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When this message was output during operation
Check that the managed network device has not been replaced with a different model.
Description
Obtaining of the configuration information from the network device device has failed.
In device, the name of the managed network device or its admin IP address is displayed.
This message is output in the following cases:
There is an error in the account information of the network device registered in Resource Orchestrator
The account information of the network device registered in Resource Orchestrator is different from that configured on the network device
The network device is not operating correctly
Corrective Action
Identify and resolve the problem based on the content displayed in detail.
After resolving the cause, perform the operation again.
"login failed"
Check the following:
Check that the account information of the network device has been registered correctly.
The account information registered in Resource Orchestrator can be retrieved using the rcxadm netconfig export command.
For Virtual Edition, for details on the rcxadm netconfig command, refer to "3.2 rcxadm netconfig" in the "Reference Guide (Command) VE".
For Cloud Edition, for details on the rcxadm netconfig command, refer to "3.7 rcxadm netconfig" in the "Reference Guide (Command/XML) CE".
For Virtual Edition, for details on the account information of network devices, refer to "8.1 Network Configuration Information" in the "Reference Guide (Command) VE".
For Cloud Edition, for details on the account information of network devices, refer to "15.7 Network Configuration Information" in the "Reference Guide (Command/XML) CE".
Confirm that the following information configured for the network device matches the information registered in Resource Orchestrator:
Admin IP Address
User Name for Remote Login
The password for remote login
For details on how to confirm the information configured for a network device, refer to the manual for that network device.
The information registered in Resource Orchestrator can be retrieved using the rcxadm netconfig export command.
- For Virtual Edition, for details on the rcxadm netconfig command, refer to "3.2 rcxadm netconfig" in the "Reference Guide (Command) VE".
- For Cloud Edition, for details on the rcxadm netconfig command, refer to "3.7 rcxadm netconfig" in the "Reference Guide (Command/XML) CE".
In other cases
Check the following:
Confirm that the network device device is powered on.
Confirm that there is no problem in the communication path from the ROR manager to the network device.
If there are any problems, resolve the cause of the problem.
Check if the network device can be connected to using the protocol (Telnet or SSH) for the login information specified in the network configuration information.
If not, resolve the cause according to the maintenance procedure of the network device displayed in device.
"agent command error"
Check the following:
Confirm that the following information configured for the network device matches the information registered in Resource Orchestrator:
Admin Password
For details on how to confirm the information configured for a network device, refer to the manual for that network device.
The information registered in Resource Orchestrator can be retrieved using the rcxadm netconfig export command.
- For Virtual Edition, for details on the rcxadm netconfig command, refer to "3.2 rcxadm netconfig" in the "Reference Guide (Command) VE".
- For Cloud Edition, for details on the rcxadm netconfig command, refer to "3.7 rcxadm netconfig" in the "Reference Guide (Command/XML) CE".
Confirm that the network device is using the correct version of firmware.
For details on how to confirm the firmware version of the network device, refer to the manual for that network device.
[Cloud Edition]
Description
The process was canceled because the VFAB "vfab" cannot link with the tenant "tenant" that can use the global pool which has the type network pool.
When there are multiple items for "vfab" and "tenant", they are displayed separated by commas.
This message is displayed in the following cases:
When registering or modifying network devices
When linking VFAB with tenants using the network pool of the global pool.
When modifying the configuration of the global pool of tenants
When adding the network pool of the global pool to the tenant linked with VFAB.
Corrective Action
When registering or modifying network devices
When linking the VFAB "vfab" with the tenant "tenant", cancel the selection of the network pool as the available global pool, and perform the operation again.
When modifying the configuration of the global pool of tenants
When the network pool of the global pool is available to the tenant "tenant", cancel linkage between the tenant "tenant" and the VFAB "vfab", and perform the operation again.
Description
When obj is "VFAB"
When a network device was created or modified
The process was canceled as the number of VFABs that execute the process on the network device netdevice exceeds the specified value.
When a network device was deleted
The process was canceled as the number of VFABs to be deleted as a result of deletion of the network device netdevice exceeds the specified value.
Corrective Action
When obj is "VFAB"
Review the following settings and modify them so the number of target VFABs is less than specified value, and then perform the operation again.
Number of Vfab elements defined in the XML file of network configuration information
Number of VFABs to be deleted
