2655-001 | Attribute resource attribute name cannot be specified when defining a new resource. |
Explanation: You specified an attribute that is not valid when a resource is defined.
User Response: Remove this attribute from the define resource call.
2655-002 | Attribute resource attribute name appears in request more than once. |
Explanation: The attribute name was specified more than once in the request.
User Response: Make sure that the attribute is specified only once in the request.
2655-003 | Class name resource class name is not recognized by this resource manager. |
Explanation: The Distributed Management Server resource manager does not recognize the named resource class as belonging to it. This is an internal error or indicates a corrupted RMC configuration.
User Response: Record the information above and contact your software service organization.
2655-004 | Could not initialize control point for the class resource class name. |
Explanation: The Distributed Management Server resource manager was unable to initialize the named resource class.
User Response: Record the information above and contact your software service organization.
2655-005 | Attribute resource attribute name must be specified when defining a new resource. |
Explanation: A required attribute was not specified when you attempted to define a new resource.
User Response: Add the missing attribute and try the define operation again.
2655-006 | A node with the hostname hostname of the node already exists. |
Explanation: The host name of each node must be unique. As a result, you cannot specify a host name that is assigned to an existing node.
User Response: Provide a unique host name.
2655-007 | An error occurred when trying to create a node hardware control resource. |
Explanation: There were problems in creating a node hardware control resource. The log entries preceding this entry should provide more information about this problem.
User Response: Record the log entries and contact your software service organization.
2655-008 | An error occurred during a rollback operation when recovering from a previous error. There will be a data inconsistency problem. |
Explanation: There were problems during a rollback operation. The error log entries prior to this entry can be used diagnose the problem.
User Response: Record the log entries and contact your software service organization.
2655-009 | An error occurred when trying to remove a node hardware control resource. |
Explanation: There were problems in removing a node hardware control resource. The log entries preceding this entry should provide more information about this problem.
User Response: Record the log entries and contact your software service organization.
2655-010 | An error occurred when trying to update a node hardware control resource. |
Explanation: There were problems when updating a node hardware control resource. The log entries preceding this entry should provide more information about this problem.
User Response: Record the log entries and contact your software service organization.
2655-011 | Incorrect number of elements in input for converting a premanaged node to a managed node |
Explanation: The required number of elements are not provided for converting a premanaged node to a managed node.
User Response: Provide the correct number of input elements.
2655-012 | Incorrect datatype for the elements in input for converting a premanaged node to a managed node. |
Explanation: The datatype of input elements is not correct.
User Response: Provide input elements with the correct datatype.
2655-013 | A node group with name NodeGroup name already exists. |
Explanation: An existing node group has the same name as the node group you specified.
User Response: Provide a unique name to the node group.
2655-014 | ValidateNodes attribute value should be 1 or 0. |
Explanation: The value assigned to the ValidateNodes attribute must be with 1 or 0.
User Response: Specify either 1 or 0 as the value for the ValidateNodes attribute.
2655-015 | Duplicate member names in list. |
Explanation: The MemberList node group resource attribute contains members that are repeated more than once.
User Response: Make sure that a value appears only once in the member list.
2655-016 | The select string specified for the node group could not be validated. Please check the select string syntax. |
Explanation: The select string does not have a valid syntax.
User Response: Provide a valid select string. Refer to IBM RSCT for Linux: Technical Reference for more information about the select string syntax.
2655-017 | Both MemberList and SelectStr attributes cannot be specified for the same node group. |
Explanation: A node group can be based on either a select string or a member list, but not both.
User Response: Provide either the MemberList attribute or the SelectStr attribute, but not both, for a node group.
2655-018 | Unable to define the node group because a row could not be added to the CSM Database. |
Explanation: There were problems when updating the database with the node group information.
User Response: Verify that the database is accessible on the management server machine.
2655-019 | The node group cannot be removed because it is a member of another NodeGroup. |
Explanation: You specified a node group that was a member of another node group.
User Response: Before attempting to remove the node group, make sure that it is not a member of any other node group.
2655-020 | Unable to remove node group Node group name because the CSM database could not be updated. |
Explanation: There were problems when updating the database with the node group information.
User Response: Verify that the database is accessible on the management server machine.
2655-021 | Unable to remove node group node group name because the CSM database could not be updated. |
Explanation: There were problems when updating the database with the node group information.
User Response: Verify that the database is accessible on the management server machine.
2655-022 | The member name Node or Nodegroup specified as part of the MemberList is not a valid node. |
Explanation: That ValidateNodes attribute was set for the node group, and the member you specified was not a node in the cluster.
User Response: Make sure that the member is a valid node in the cluster.
2655-023 | The NodeGroup NodeGroup name cannot be added as a member of the node group because it leads to cyclic dependency between the node groups. |
Explanation: None.
User Response: Do not attempt to add the node group to this node group.
2655-024 | The ValidateNodes attribute is not set for node group Node Group name, so it cannot be added as a member of the node group for which the ValidateNodes attribute is set. |
Explanation: If the ValidateNodes attribute is set for a node group, then any node group added to its member list must have its ValidateNodes attribute set.
User Response: Do not attempt to add a node group that does not have its ValidateNodes attribute set to this node group.
2655-025 | Unexpected error in method method name. |
Explanation: There were errors in the method. The log entries preceding this entry should provide more information about this problem.
User Response: Record the log entries and contact your software service organization.
2655-026 | MemberList attribute cannot be specified for the node group because the SelectStr attribute is set. |
Explanation:
User Response: Before attempting to set the MemberList attribute, set the SelectStr attribute to an empty string.
2655-027 | SelectStr attributes cannot be specified for the node group because the MemberList attribute is set. |
Explanation:
User Response: Before attempting to set the SelectStr attribute, set the MemberList attribute to have no members.
2655-028 | Incorrect number of fields in input to action action name. |
Explanation: The required number of elements are not provided for the action.
User Response: Provide the correct number of input elements.
2655-029 | Incorrect datatype for the elements in input to action action name. |
Explanation: The data type of input elements is not correct.
User Response: Provide input elements with the correct data type.
2655-030 | At least one of the member names in input list already exists in the node group current member list. |
Explanation: One or more members of the input list is already a member of the node group.
User Response: Make sure that none of the member names in the input list is an existing member of the node group.
2655-031 | Number of nodes in the domain exceeded the maximum limit of maximum number of nodes allowed in the domain. Node was not defined to the management domain. |
Explanation:
User Response: Either remove an existing node before adding this node, or purchase a version of CSM that allows a higher scaling limit.
2655-032 | A node with the specified node identifier exists in the management domain. |
Explanation: None.
User Response: None.
2655-033 | Unable to select the node resource to be updated because there are two ManagedNode resources; one matching the hostname and the other matching the specified universal id. |
Explanation: None.
User Response: None.
2655-034 | Unable to select the node resource to be updated because the ManagedNode resource matching the specified hostname has an universal id that is different from the specified universal id. |
Explanation: None.
User Response: None.
2655-035 | Hostname attribute value specified for the node is not valid. |
Explanation: The Hostname attribute value must be a non-zero length string.
User Response: Provide a valid value for the hostname attribute.
2655-036 | An error occurred when updating the distributed domain information in the RMC subsystem. |
Explanation: There were problems when updating the node or node group information that belongs to the distribute domain.
User Response: Record the information above and contact your software service organization.
2655-037 | An error occurred when updating the CSM database. |
Explanation: There were problems when updating the database.
User Response: Verify that the database is accessible on the management server machine.
2655-038 | An error occurred when verifying the validity of the request from the node. |
Explanation: There were problems when verifying that the node is allowed to make a request to manage the management server. The log entries preceding this entry should provide more information about this problem.
User Response: Record the log entries and contact your software service organization.
2655-039 | The exchange of public key between the node and the management server is not allowed. |
Explanation: The node is not allowed to make a request to exchange the public key with the management server. At least one of the following three conditions must be satisfied to allow the public key exchange:
User Response: Make sure that at least one of the condition mentioned in the explanation above is satisfied.
2655-040 | An error occurred when storing the public key of the node node name to the trusted host list file on the management server. |
Explanation: There were problems when attempting to store the node's public key in the trusted host list file on the management server.
User Response: Record the log entries and contact your software service organization.
2655-041 | An error occurred when retrieving the public key of the management server. |
Explanation: There were problems in obtaining the public key of the management server machine.
User Response: Record the log entries and contact your software service organization.
2655-042 | An error occurred when preparing the response. |
Explanation: There were problems in preparing a response to an action request. This is an internal error.
User Response: Record the log entries and contact your software service organization.
2655-043 | The management server is not authorized to accept the manage request from the node. |
Explanation: The node is not allowed to make the request to the management server. At least one of the following three conditions must be satisfied for the management server to accept the node's request:
User Response: Make sure that at least one of the conditions mentioned in the explanation above is satisfied.
2655-044 | Create or Update of the node resource failed. |
Explanation: There were problems when creating or updating a managed node. The log entries preceding this entry should provide more information about this problem.
User Response: Record the log entries and contact your software service organization.
2655-045 | An error occurred when creating the message signature. |
Explanation: None.
User Response: None.
2655-046 | An error occurred when verifying the message signature. |
Explanation: None.
User Response: None.
2655-047 | An error occurred when initializing the logging facility. The return code was return code and the error message was error message. |
Explanation: None.
User Response: None.
2655-048 | An error occurred when initializing the logging facility. The return code was return code. |
Explanation: None.
User Response: None.
2655-049 | The following error message was returned by function function name: error message. |
Explanation: None.
User Response: None.
2655-050 | Invalid input to action. |
Explanation: None.
User Response: None.
2655-051 | Unable to set RMC subsystem as a distinguished daemon. Return code is return code. |
Explanation: None.
User Response: None.
2655-052 | Failed to remove ManagementServer resource entry on node node name. |
Explanation: None.
User Response: None.
2655-053 | The SelectStr attribute can be specified for a node group only if the ValidateNodes attribute is set to 1. |
Explanation: None.
User Response: Make sure that the ValidateNodes attribute is set to 1 for the node group.
2655-054 | AddUnrecognizedNode attribute value should be 1 or 0. |
Explanation: The value assigned to AddUnrecognizedNode attribute must be either 1 or 0.
User Response: Specify either 0 or 1 as value for the AddUnrecognizedNode attribute.
2655-055 | The valid values for AllowManageRequest attribute are 0 or 1. |
Explanation: The value assigned to AllowManageRequest attribute must be 0 or 1.
User Response: Specify 0 or 1 as value for the AllowManageRequest attribute.
2655-056 | The member name node group name specified as part of the MemberList is not a valid node group. |
Explanation: The member you specified was not an existing node group.
User Response: Ensure that the member is an existing node group.
2655-057 | Could not find a resource corresponding to this management server on the node. |
Explanation: None.
User Response: Ensure that the node is managed by this management server.
2655-058 | Unable to retrieve the hostname of the node or the management server name as known to the node. |
Explanation: None.
User Response: None.
2655-200 | Bad or missing parameters to invocation of class action. |
Explanation: None.
User Response: None.
2655-201 | Node was not authenticated -- action ignored. |
Explanation: None.
User Response: None.
2655-202 | Unable to update RMC acl file. |
Explanation: None.
User Response: None.
2655-203 | Unable to store the public key of the node. |
Explanation: None.
User Response: None.
2655-204 | Memory allocation error while preparing action response. |
Explanation: None.
User Response: None.
2655-205 | Input to NodeHwCtrl resource class action, powerAction, is not valid. |
Explanation: NodeHwCtrl resource class action, powerAction requires structure data input elements:
User Response: Ensure that the proper structured data members are passed into the action.
2655-206 | Could not find hardware control point for the node. |
Explanation: None.
User Response: None.
2655-207 | Could not load hardware control library. |
Explanation: None.
User Response: None.
2655-208 | Could not perform action because one or more node attributes HWControlPoint, HWControlNodeId or PowerMethod are not set. |
Explanation: The node attributes, HWControlPoint, HWControlNodeId and PowerMethod must be defined to perform the power action.
User Response: Use the chnode command to add valid values to the node object.
2655-209 | Hostname attribute value specified for the node is not valid. |
Explanation: The Hostname attribute value must be a non-zero length string.
User Response: Provide a valid value for the Hostname attribute.