3.1.4 Error Messages

The error messages displayed by Cluster Admin are described in message number sequence.

2000 : Error getting nodes or no active nodes to manage.

Content:

An internal error occurred in the program.

Corrective action:

Record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."

2001: Error in loading image: image.

Content:

An internal error occurred in the program.

Corrective action:

2002: Timeout checking installed packages.

Content:

An internal error occurred in the program.

Corrective action:

2004 : Connection to port port on host node failed: message.
Please Verify node name, port number, and that the web server is running.

Content:

An internal error occurred in the program.

Corrective action:

2010 : No node object for: node.

Content:

An internal error occurred in the program.

Corrective action:

2011 : Unknown data stream.

Content:

An internal error occurred in the program.

Corrective action:

2013 : Finished searching the document.

Content:

No results found for the specified filter criteria for log messages.

Corrective action:

Change the filter criteria.

2014 : File not found.

Content:

An internal error occurred in the program.

Corrective action:

2016 : Invalid time range.

Content:

The start time has been set after the end time for filtering log messages in logviewer.

Corrective action:

Change the time range.

2017 : Unknown Message Identifier in resource file:

Content:

An internal error occurred in the program.

Corrective action:

2018 : Illegal arguments for Message Identifier:

Content:

An internal error occurred in the program.

Corrective action:

2020 : Start time is invalid.

Content:

The start time is not correct for searching messages in log viewer.

Corrective action:

Correct the start time.

2021 : End time is invalid.

Content:

The end time is not correct for searching messages in log viewer.

Corrective action:

Correct the end time.

2501 :There was an error loading the driver:

Content:

An internal error occurred in the program.

Corrective action:

2502 :There was an error unloading the driver:

Content:

An internal error occurred in the program.

Corrective action:

2504 :There was an error unconfiguring CF:

Content:

An internal error occurred in the program.

Corrective action:

2505 :There was an error communicating with the back end:

Content:

Cluster Admin failed to get the host name corresponding to mip of Web-Based Admin View.

Corrective action:

Execute the following command on all cluster nodes to check the mip value.

# /etc/opt/FJSVwvbs/etc/bin/wvGetparam mip

Describe the mip value checked above and its corresponding host name to the hosts file on all the cluster nodes.

For details on mip, see "Environment variable" in "PRIMECLUSTER Web-Based Admin View Operation Guide."

For details on the wvGetparam command, see "Web-Based Admin View" of "PRIMECLUSTER Installation and Administration Guide."

For the hosts file, check the following:

Solaris
/etc/inet/hosts
Linux
/etc/hosts

2506 :There are no nodes in a state that can be stopped.

Content:

There are no nodes in a state that can be stopped.

Corrective action:

There are no nodes in a state that can be stopped. Node should be in one of these states to be stopped: UP, INVALID, COMINGUP, or LOADED.

2507 :Error starting CF on node:

Content:

An internal error occurred in the program.

Corrective action:

2508 :Error listing services running on node:

Content:

An internal error occurred in the program.

Corrective action:

2510 :Error stopping CF on node:

Content:

An internal error occurred in the program.

Corrective action:

2511 :Error stopping service on node:

Content:

An internal error occurred in the program.

Corrective action:

2512 :Error clearing statistics on node:

Content:

An internal error occurred in the program.

Corrective action:

2513 :Error marking down node:

Content:

Error occurred when marking nodes as DOWN.

Corrective action:

Error occurred when marking nodes as DOWN. The nodes should be in the LEFTCLUSTER state to be able to mark down.

2514 :To start CF on the local node, click on the appropriate button in the left hand panel.To start CF on a remote node, CF must be running on the local node.

Content:

To start CF on the local node, click on the appropriate button in the left hand panel. To start CF on a remote node, CF must be running on the local node.

Corrective action:

Start CF on the local node by clicking on the appropriate button in the left hand panel. To start CF on a remote node, CF must be running on the local node.

2515 :To unconfigure CF on the local node, click on the appropriate button in the left hand panel.To unconfigure CF on a remote node, CF must be running on the local node.

Content:

To unconfigure CF on the local node, click on the appropriate button in the left hand panel. To unconfigure CF on a remote node, CF must be running on the local node.

Corrective action:

Unconfigure CF on the local node by clicking on the appropriate button in the left hand panel. To unconfigure CF on a remote node, CF must be running on the local node.

2516 :CF is not running on the local node, and cannot be stopped.To stop CF on a remote node, CF must be running on the local node.

Content:

CF is not running on the local node, and cannot be stopped. To stop CF on a remote node, CF must be running on the local node.

Corrective action:

CF is not running on the local node, and cannot be stopped. To stop CF on a remote node, CF must be running on the local node.

2517 :In order to mark nodes as DOWN, CF must be running on the local node.

Content:

To mark nodes as DOWN, CF must be running on the local node.

Corrective action:

To mark nodes as DOWN, start CF on local node by clicking on the appropriate button in the left hand panel.

2518 :In order to display network topology, CF must be running on the local node.

Content:

To display network topology, CF must be running on the local node.

Corrective action:

To display network topology, start CF on local node by clicking on the appropriate button in the left hand panel.

2519 :In order to display any statistics, CF must be running on the local node.

Content:

To display any statistics, CF must be running on the local node.

Corrective action:

To display any statistics, start CF on local node by clicking on the appropriate button in the left hand panel.

2520 :In order to clear statistics, CF must be running on the local node.

Content:

To clear statistics, CF must be running on the local node.

Corrective action:

To clear statistics, start CF on local node by clicking on the appropriate button in the left hand panel.

2521 :There are no nodes in a state where statistics can be displayed.

Content:

There are no nodes in a state where statistics can be displayed.

Corrective action:

There are no nodes in a state where statistics can be displayed. Node should be in UP state for this operation.

2522 :There are no nodes in a state where messages can be displayed.

Content:

There are no nodes in a state where messages can be displayed.

Corrective action:

There are no nodes in a state where messages can be displayed. Node should not be UNKNOWN state for this operation.

2523 :There are no nodes in a state where they can be started.

Content:

There are no nodes in a state where they can be started.

Corrective action:

There are no nodes in a state where they can be started. Node should be in one of these states for this operation: LOADED, UNLOADED, or NOT_INITED.

2524 :There are no nodes in a state where they can be unconfigured.

Content:

There are no nodes in a state where they can be unconfigured.

Corrective action:

There are no nodes in a state where they can be unconfigured. Node should be in one of these states for this operation: LOADED, UNLOADED, or NOT_INITED.

2526 :Error scanning for clusters:

Content:

An internal error occurred in the program.

Corrective action:

2528 :Please select a cluster to join.

2529 :The specified cluster name is already in use.

Content:

The specified cluster name is already in use.

Corrective action:

Please use other cluster name.

2532 :Probing some nodes failed. See status window for details.

Content:

An internal error occurred in the program.

Corrective action:

2533 :Some nodes failed CIP configuration.

Content:

An internal error occurred in the program.

Corrective action:

2534 :Insufficient IPs for net net available in /etc/hosts. There are not enough unassigned IPs in /etc/hosts on the cluster nodes. Please remove any unneeded addresses for this subnet from /etc/hosts, or use a different subnet.

2535 :Missing node suffix for net net.

Content:

The node suffix has not been entered.

Corrective action:

Please provide the node suffix.

2536 :The node suffix for net net is too long.

Content:

The node suffix is too long.

Corrective action:

The node suffix should be less than or equal to 10.

2537 :Invalid node suffix for net net. Node names may only contain letters, numbers, and - characters.

Content:

Invalid node suffix. Node names may only contain letters, numbers, and - characters.

Corrective action:

Enter valid node suffix.

2538 :Invalid subnet mask for net net. The subnet mask must be in the form of 4 numbers 0-255 separated by dots. Also, when written in binary, it must have all 1s before 0s.

Content:

Invalid subnet mask. The subnet mask must be in the form of 4 numbers 0-255 separated by dots. Also, when written in binary, it must have all 1s before 0s.

Corrective action:

Enter valid subnet mask.

2539 :Invalid subnet number for net net. The subnet number must be in the form of 4 numbers 0-255 separated by dots.

Content:

Invalid subnet number. The subnet number must be in the form of 4 numbers 0-255 separated by dots.

Corrective action:

Enter valid subnet number.

2540 :net net is too small.The cluster has number of nodes nodes. Only number of nodes possible host ids is supported by the IP subnet and netmask given for net net. Please use a subnet and netmask combination that has more host ids.

Content:

IP/netmask combination is too small.

Corrective action:

Please use a subnet and netmask combination that has more host IDs.

2541 :The IP range ip1/netmask1 overlaps with ip2/netmask2, which is in use on node.

Note

ip1

In IPv4, the subnet number on the screen is displayed.

In IPv6, the network prefix on the screen is displayed.

ip2

In IPv4, the IPv4 address being activated in the network interface on node is displayed.

In IPv6, the IPv6 address being activated in the network interface on node is displayed.

netmask1 netmask2

In IPv4, the subnet mask is displayed.

In IPv6, the prefix-length is displayed.

Content:

IPv4
The networks for the subnet number (ip1) and the subnet mask (netmask1), and the IPv4 address (ip2) being activated in the network interface on node and the subnet mask (netmask2) overlap with each other.
IPv6
The networks for the network prefix (ip1) and the prefix-length (netmask1), and the IPv6 address (ip2) being activated in the network interface on node and the prefix-length (netmask2) overlap with each other.

Corrective action:

For IPv4, use the subnet number and the subnet mask that become other network.

For IPv6, use the network prefix and the prefix-length that become other network.

2542 :The IP ranges for net net1 and net net2 overlap.

Content:

The IP/netmask combination provided overlaps with each other.

Corrective action:

Please use other IP/netmask combination.

2543 :The subnet subnet has no nodes on it.

Content:

There are no nodes on the subnet.

Corrective action:

Please select some node from the list.

2544 :There are no nodes in a LEFTCLUSTER state.

Content:

There are no nodes in a LEFTCLUSTER state.

Corrective action:

This option is valid when there is some node in LEFTCLUSTER state.

2549 :Error adding node to CIM:

Content:

An internal error occurred in the program.

Corrective action:

2550 :Error removing node from CIM:

Content:

An internal error occurred in the program.

Corrective action:

2551 :In order to add nodes to CIM, CF must be running on the local node.

Content:

To add nodes to CIM, CF must be running on the local node.

Corrective action:

Bring CF UP on the local node.

2552 :In order to remove nodes from CIM, CF must be running on the local node.

Content:

To remove nodes from CIM, CF must be running on the local node.

Corrective action:

Bring CF UP on the local node.

2553 :There are no nodes in a state where they can be added to CIM.

Content:

There are no nodes in a state where they can be added to CIM.

Corrective action:

To add a node to CIM, CF should be UP on the node and the node should not be already added to CIM.

2554 :There are no nodes in a state where they can be removed from CIM.

Content:

There are no nodes in a state where they can be removed from CIM.

Corrective action:

To remove a node from CIM, CF should be UP on the node and the node should be already added to CIM.

2556 :CIM Configuration failed.

Content:

An internal error occurred in the program.

Corrective action:

2557 :Please select a node to add.

2558 :Please select a node to remove.

2559 :Nodes already in the cluster cannot be removed.

Content:

An internal error occurred in the program.

Corrective action:

2560 :The local node cannot be removed.

Content:

An internal error occurred in the program.

Corrective action:

2561 :Some nodes were not stopped. See status window for details.

Content:

An internal error occurred in the program.

Corrective action:

2562 :Some nodes failed CF configuration.

Content:

An internal error occurred in the program.

Corrective action:

2563 :Error adding CIM override on node:

Content:

An internal error occurred in the program.

Corrective action:

2564 :Error removing CIM override on node:

Content:

An internal error occurred in the program.

Corrective action:

2565 :In order to override CIM, CF must be running on the local node.

Content:

To override CIM, CF must be running on the local node.

Corrective action:

To override CIM, CF must be running on the local node.

2566 :In order to remove CIM override, CF must be running on the local node.

Content:

To remove CIM override, CF must be running on the local node.

Corrective action:

To remove CIM override, CF must be running on the local node.

2567 :There are no nodes in a state where they can be overridden.

Content:

There are no nodes in a state where they can be overridden.

Corrective action:

To add a node to CIM, CF should be UP on the node and the node should not be already added to CIM.

2568 :There are no nodes in a state that can have a CIM override removed.

Content:

There are no nodes in a state that can have a CIM override removed.

Corrective action:

To remove a node from CIM, node should be already added to CIM.

2578 :For node, the IP address for interconnect interconnect_name and interconnect interconnect_name are the same.

Content:

IP address for the two interconnects are the same.

Corrective action:

For node, the IP address for interconnects are the same. Please use distinct IP address for the two interconnects.

2579 :The address for node on interconnect interconnect_name is missing.

Content:

The address for interconnect has not been selected.

Corrective action:

The address for node on interconnect is missing. Please select the appropriate address from the dropdown.

2580 :The IP address and broadcast address for node on interconnect interconnect_name are not consistent with each other.

Content:

The IP address and broadcast address for interconnect are not consistent with each other.

Corrective action:

The IP address and broadcast address for interconnect must be consistent with each other.

2582 :In order to check heartbeats, CF must be running on the local node.

2583 :For interconnect interconnect_name, the IP address for node is not on the same subnet as the IP address for node.

Content:

For interconnects, the IP address for nodes is not on the same subnet.

Corrective action:

For interconnects, the IP address for nodes is not on the same subnet. For one interconnect, IP address should be in the same subnet on all the cluster nodes.

2585 :On interconnect interconnect_name, the IP address for node node and node node are the same.

Content:

The IP addresses for two nodes on interconnect is the same.

Corrective action:

The IP addresses for two nodes on interconnect is the same. Please make the appropriate change.

2586 :Invalid CF node name for node. Lowercase a-z, 0-9, _ and - are allowed.

Content:

Invalid CF name for node. Lowercase a-z, 0-9, _ and - are allowed.

Corrective action:

Invalid CF name for node. Lowercase a-z, 0-9, _ and - are allowed. Please enter valid CF name.

2587 :The CF node name for node1 and node2 are the same.

Content:

The CF name for two nodes is the same.

Corrective action:

The CF name for two nodes is the same. Please select a different CF name.

2588 :The CF node name for node is empty.

Content:

The CF name is empty.

Corrective action:

The CF name is empty. Please enter/select the CF name.

2590 :Invalid cluster name. The cluster name may contain letters, numbers, dashes, and underscores.

Content:

Invalid cluster name. Letters, numbers, dashes, and underscores are only available for the cluster name.

Corrective action:

Enter a valid cluster name.

2591 :The CF node name for node1 is the same as the public name of node2.

Content:

The CF name for node is the same as the public name of other node.

Corrective action:

The CF name for node is the same as the public name of other node. Please choose a different CF name for node.

2594 :CF is not running on the local node. To check CF for unload, CF must be running on the local node.

2595 :There are no nodes in a state where the unload status can be checked.

Content:

There are no nodes in a state where the unload status can be checked.

Corrective action:

There are no nodes in a state where the unload status can be checked. At least one node should be in UP state.

2600 :For node, the interfaces for interconnect interconnect_name and interconnect interconnect_name are on the same subnet.

Content:

There are multiple interfaces for interconnects on the same subnet.

Corrective action:

There are multiple interfaces for interconnects on the same subnet. Please use separate subnet.

2921 :Internal Error:SF Wizard:Unable to run command on node.

Content:

An internal error occurred in the program.

Corrective action:

2922 :Internal Error:SF Wizard:Error reading file file from node.

Content:

An internal error occurred in the program.

Corrective action:

2923 :Internal Error:SF Wizard:Reading file :Ignoring Unknown data:

Content:

An internal error occurred in the program.

Corrective action:

2925 :Internal Error:SF Wizard:Unknown data: SA_xcsf.

Content:

An internal error occurred in the program.

Corrective action:

2926 :Passwords do not match. Retype.

2939 :Internal Error:SF Wizard:Empty data, not writing to file file on node.

Content:

An internal error occurred in the program.

Corrective action:

2940 :Internal Error:SF Wizard:Error writing to file file on node.

Content:

An internal error occurred in the program.

Corrective action:

2941 :You must enter weight for each of the CF nodes.

2942 :Invalid CF node weight entered.

2943 :You must enter admin IP for each of the CF nodes.

2944 :CF node weight must be between 1 and 300.

2946 :You must select at least one agent to continue.

2946 :You must select one agent to continue. (Solaris 4.3A10 or later)

2947 :Timeout value must be an integer greater that zero and less than 3600.

2948 :Shutdown Facility reconfiguration failed on node.

Content:

An internal error occurred in the program.

Corrective action:

2950 :You must specify XSCF-Name and User-Name for each of the CF nodes.

2952 :You must specify RCCU-Name for each of the CF nodes.

2959 :Timeout value is out of range.

Content:

Timeout value is out of range.

Corrective action:

Timeout value must be less than 3600.

2960 :You must specify a MMB User-Name for each of the hosts.

2961 :The MMB User-Name must be between 8 and 16 characters long.

2962 :The MMB Password must be between 8 and 16 characters long.

2963 :The MMB Panic Agent must have higher precedence than the MMB Reset Agent.

2967 :You must specify ILOM-name and User-Name for each of the CF nodes.

2968 :You must specify ALOM-name and User-Name for each of the CF nodes.

2969 :You must specify a unique hostname or IP address for XSCF Name1 and XSCF Name2.

2970 :You must specify XSCF Password for each of the CF nodes.

2971 :You must specify ILOM Password for each of the CF nodes.

2972 :You must specify ALOM Password for each of the CF nodes.

2973 :Invalid network prefix for net{0}. The subnet number must be in the form of hexadecimal numbers separated by colons.

Content:

Invalid network prefix.

Corrective action:

Enter valid network prefix.

The network prefix must satisfy the following conditions:

No more than one "::" should exist.
The end of the prefix must not be ":" (except when the end is ::).
The field numbers separated by ":" must be eight or less.
If the field numbers separated by ":" is less than eight, "::" must be included.
Each filed separated by ":" must be 0 to 4 digits.
The character or letter for each field separated by ":" must be 0 to 9, a to f, or A to F.

2974 :net {0} does not have enough address space.
The cluster has {2} nodes. Only {1} possible host ids are supported by the network prefix given for net {0}. Please use network prefix andprefix-length combination that has more host ids.

Content:

The combination of the network prefix and prefix- length is small.

Corrective action:

Please use the network prefix and prefix-length combination that has more host IDs.

2975 :Invalid prefix-length for net{0}. The prefix-length must be specified in the range of from 64 to 128.

Content:

Invalid prefix-length. The prefix-length must be specified in the range of from 64 to 128.

Corrective action:

Enter valid prefix-length.

2976 :The nodesuffix of net{0} and net{1} overlaps.

Content:

The nodesuffix of net{0} and net{1} overlaps.

Corrective action:

Enter unique nodesuffix to multiple CIP subnets respectively.

2977 :"RMS" was entered to the nodesuffix of net{0}.
If you want to use "RMS" to the nodesuffix, select "For RMS".

Content:

"RMS" was entered to the nodesuffix of net {0} even though "For RMS" has not been selected.

Corrective action:

If you want to use "RMS" to the nodesuffix, select "For RMS."

2978 :The first character of CF node name node is not a lower case letter.
RMS Wizard Tools cannot operate by this CF node name.
Please use a lower case letter to the first character of CF node name.

Content:

Invalid CF name for node. The first character of CF name must be a lower case letter (from a to z).

Corrective action:

Use the first character of CF name, use a lower case letter (from a to z).

2980 :Failed to get domain information of OVM on the CF node <CF nodename>.
Please confirm the OS's release is "Oracle Solaris 11" or higher than "Oracle Solaris 10 9/10"and that the domain type is control domain or guest domain.

Content:

Failed to get OVM(Oracle VM for SPARC).

Corrective action:

Check whether the following conditions are satisfied. Then, check that OVM (Oracle VM for SPARC) can be obtained in the environment.

Oracle Solaris 10 9/10 must be used.
The environment must support OVM.
It must be global zone.

The domain information can be obtained with the /usr/sbin/virtinfo -ap command.

Example

$ virtinfo -ap
VERSION 1.0
DOMAINROLE|impl=LDoms|control=true|io=true|service=true|root=true
DOMAINNAME|name=primary
DOMAINUUID|uuid=8e0d6ec5-cd55-e57f-ae9f-b4cc050999a4
DOMAINCONTROL|name=san-t2k-6
DOMAINCHASSIS|serialno=0704RB0280

2981 :PPAR-ID of the CF node <CF nodename> is invalid.
Please input the numerical value within the range of 0-15 to PPAR-ID.

Content:

PPAR-ID of <CF nodename> is invalid.

Corrective action:

Input the numerical value within the range of 0 to 15 to PPAR-ID.

2982 :The domain name of the CF node <CF nodename> is invalid.
Please enter correct name to domain name.

Content:

The domain name of <CF nodename> is invalid.

Corrective action:

Enter the correct domain name under the following rules:

The character string must be up to 255 and it must include alphabets, numbers, - (a hyphen), and . (a period).
The first character must be an alphabet.

2983 :You must specify XSCF-Name1 of the CF node <CF nodename>.

Content:

XSCF-Name1 of <CF nodename> has not been specified.

Corrective action:

Specify the host name or the IPv4 address for XSCF-Name1 of <CF nodename>.

2984 :You must specify XSCF-Name2 of the CF node <CF nodename>.

Content:

XSCF-Name2 of <CF nodename> has not been specified.

Corrective action:

Specify the host name or the IPv4 address for XSCF-Name2 of <CF nodename>.

2985 :You must specify user of the CF node <CF nodename>.

Content:

The User-Name in <CF nodename> line is not specified.

Corrective action:

Input the correct user name to User-Name.

2986 :You must specify Password of the CF node <CF nodename>.

Content:

The password of the <CF nodename> is not entered.

Corrective action:

Enter the password of the <CF nodename>.

2987 :You must specify a unique hostname or IP address for XSCF Name1 and XSCF Name2 of the CF node <CF nodename>.

Content:

The XSCF Name1 and XSCF Name2 of <CF nodename> overlap.

Corrective action:

Specify the different host name or IP address for the XSCF Name1 and XSCF Name2 of <CF nodename> respectively.

2988 :Passwords of the CF node <CF nodename> do not match. Please retry.

Content:

Passwords of <CF nodename> do no match.

Corrective action:

Re-enter the correct password of <CF nodename>.

2991 :You must specify Unit Name of the CF node <CF nodename> in the line <line number>.

Content:

The unit name of the <CF nodename> in the line <line number> is not entered.

Corrective action:

Enter the IPv4 address for the unit name.

2992 :Outlet of the CF node <CF nodename> in the line <line number> is invalid. Please input the numerical value within the range of 1-8 to Outlet.

Content:

The outlet number of <CF nodename> in the line <line number> is invalid.

Corrective action:

Input the numerical value within the range of 1 to 8 to Outlet.

2993 :You must specify zonename of the CF node <CF nodename>.

Content:

The zonename of <CF nodename> is not entered.

Corrective action:

Enter the zonename of <CF nodename>.

2994 :You must specify global zone hostname of the CF node <CF nodename>.

Content:

The global zone host name of <CF nodename> is not entered.

Corrective action:

Enter the host name or the IP address for the global zone host name of <CF nodename>.

2995 :You must specify ILOM-name of the CF node <CF nodename>.

Content:

The ILOM name of <CF nodename> is not entered.

Corrective action:

Enter the host name or the IP address for the ILOM name of <CF nodename>.

2996 :You must specify User-Name of the CF node <CF nodename> in the line <line number>.

Content:

The user name of the <CF nodename> in the line <line number> is not entered.

Corrective action:

Enter the user name of the <CF nodename> in the line <line number>.

2997 :You must specify Password of the CF node <CF nodename> in the line <line number>.

Content:

The password of the <CF nodename> in the line <line number> is not entered.

Corrective action:

Enter the password of the <CF nodename> in the line <line number>.

2998 :Passwords of the CF node <CF nodename> in the line <line number> do not match. Please retry.

Content:

The password entered does not match the password of <CF nodename> in the line <line number>.

Corrective action:

Enter the password of the <CF nodename> in the line <line number> again.

3000 : Fatal Error processor internal:RMS session is null.

Content:

An internal error occurred in the program.

Corrective action:

3001 : Fatal Error processor internal:RMS session graph is null.

Content:

An internal error occurred in the program.

Corrective action:

3002 : Fatal Error processor internal:Not initialized as local or remote.

Content:

An internal error occurred in the program.

Corrective action:

3003 : Error: Unable to get remote stream reader.

Content:

An internal error occurred in the program.

Corrective action:

3004 : Error: Unable to obtain remote data stream : message.

Content:

An internal error occurred in the program.

Corrective action:

3005 : Error: new Thread() failed for "" node.

Content:

An internal error occurred in the program.

Corrective action:

3006 : Error: Reconnect failed. Data displayed for node will no longer be current.

Content:

An internal error occurred in the program.

Corrective action:

3010 : Error: Exception while closing data reader: message.

Content:

An internal error occurred in the program.

Corrective action:

3012 : Error: RMS and GUI are not compatible. Use newer version of RMS GUI.

Content:

An internal error occurred in the program.

Corrective action:

3013 : Error: Missing local host indication from node.

Content:

An internal error occurred in the program.

Corrective action:

3016 : Error INTERNAL: exception while reading line :

Content:

An internal error occurred in the program.

Corrective action:

3018 : Error: Missing SysNode name declaration block.

Content:

An internal error occurred in the program.

Corrective action:

3021 : Error node : Missing token.

Content:

An internal error occurred in the program.

Corrective action:

3024 : Received Error: message.

Content:

An internal error occurred in the program.

Corrective action:

3026 : Error: Connection to node node failed.

Content:

An internal error occurred in the program.

Corrective action:

3028 : Error: Connections to all hosts failed.

Content:

Connections to all hosts failed.

Corrective action:

No action is required. GUI retries to connect to all hosts.

3030:Unable to shutdown RMS on node.

Content:

An internal error occurred in the program.

Corrective action:

3031:Error returned from hvshut. Click "msg" tab for details.

Content:

An internal error occurred in the program.

Corrective action:

3040:switchlog Error: R=null.

Content:

The switchlog cannot be shown for the node where RMS is down.

Corrective action:

Bring the RMS Online on the node.

3042:Error Intern: Nodecmd.exec() R==null.

Content:

An internal error occurred in the program.

Corrective action:

3043:Error: Remote connection to node failed, Exception: message.

Content:

An internal error occurred in the program.

Corrective action:

3044:Error: Invoking remote application command on node exited with the following error: message.

Content:

An internal error occurred in the program.

Corrective action:

3072:Error: SysNode node_name points to node_kind node_name.

Content:

An internal error occurred in the program.

Corrective action:

3088:empty graph.

Content:

An internal error occurred in the program.

Corrective action:

3089:Graph has only number_of_nodes disjoint nodes and no arcs.

Content:

An internal error occurred in the program.

Corrective action:

3091:Application is inconsistent. Analyse configuration before applying any RMS operation.

Content:

An internal error occurred in the program.

Corrective action:

3102:Internal Error: Unknown node type: node_type.

Content:

An internal error occurred in the program.

Corrective action:

3130:Error in loading image: image_name.

Content:

An internal error occurred in the program.

Corrective action:

3131=Fatal Error clusterTable: No clusterWide in clusterTable.

Content:

An internal error occurred in the program.

Corrective action:

3132=Fatal Error clusterTable: No tableLayout in clusterTable.

Content:

An internal error occurred in the program.

Corrective action:

3133=Fatal Error clusterWide: no pointer to rmsCluster.

Content:

An internal error occurred in the program.

Corrective action:

3134=Fatal Error clusterWide: no pointer to session.

Content:

An internal error occurred in the program.

Corrective action:

3135=Fatal Error clusterWide: update_display called without cluster_table.

Content:

An internal error occurred in the program.

Corrective action:

3136=Fatal Error nodeTable: No layout in nodeTable.

Content:

An internal error occurred in the program.

Corrective action:

3137=Fatal Error nodeTable: Null value at row row and at column column.

Content:

An internal error occurred in the program.

Corrective action:

3143=Error: No output received from command rcinfo.

Content:

An internal error occurred in the program.

Corrective action:

3156:Error: Unable to get HV_RCSTART value on node.

Content:

Getting the HV_RCSTART value on node has failed.

Corrective action:

Start Web-Based Admin View and CF on all the nodes that configure the cluster.

For information on how to restart Web-Based Admin View, see "Restart" in "PRIMECLUSTER Web-Based Admin View Operation Guide."

For information on how to check the status of CF and how to start CF, see "Main CF table" and "Starting and stopping CF" in "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."

If this error message is displayed again even after you apply the above corrective action, collect the Java console information, a hard copy of the error dialog box, and investigation information, and then contact field engineers.

3157:Error: Unable to get HV_AUTOSTARTUP value on node.

Content:

Getting the HV_AUTOSTARTUP value on node has failed.

Corrective action:

Start Web-Based Admin View and CF on all the nodes that configure the cluster.

For information on how to restart Web-Based Admin View, see "Restart" in "PRIMECLUSTER Web-Based Admin View Operation Guide."

3158:Error: Unable to set HV_RCSTART value on node.

Content:

Setting the HV_RCSTART value on node has failed.

Corrective action:

Start Web-Based Admin View and CF on all the nodes that configure the cluster.

For information on how to restart Web-Based Admin View, see "Restart" in "PRIMECLUSTER Web-Based Admin View Operation Guide."

3159:Error: Unable to set HV_AUTOSTARTUP value on node.

Content:

Setting the HV_AUTOSTARTUP value on node has failed.

Corrective action:

Start Web-Based Admin View and CF on all the nodes that configure the cluster.

For information on how to restart Web-Based Admin View, see "Restart" in "PRIMECLUSTER Web-Based Admin View Operation Guide."