2653-021 | Could not execute the command that could not be executed command. |
Explanation: An error occurred when attempting to run this command.
User Response: Try running the command directly from the command line to diagnose the problem.
2653-022 | Could not find file name in path in which file name searched. |
Explanation: None.
User Response: Check for the specified file in the path given.
2653-023 | file name does not exist. |
Explanation: The file or command does not exist.
User Response: Ensure that the file can be located. Otherwise, the file may need to be installed.
2653-024 | Node install -- Failed. |
Explanation: None.
User Response: None.
2653-025 | An error occurred while installing CSM packages. |
Explanation: The install command failed.
User Response: Check previous error messages. Try installing packages manually.
2653-026 | An error occurred while attempting to execute the mgmtsvr command. |
Explanation: Could not run the mgmtsvr command.
User Response: Use error messages and CSM documentation to solve the problem.
2653-027 | Management server must be provided. |
Explanation: The name of the management server was not provided when the command was called.
User Response: None.
2653-028 | Cannot provide -n and -M together. |
Explanation: None.
User Response: None.
2653-029 | The node hostname must be provided. |
Explanation: The node host name was not provided when the command was called.
User Response: None.
2653-030 | The command that failed failed with a return code of return code (integer) of failed program or command. |
Explanation: None.
User Response: Use the return code to diagnose the error, and then issue the command again.
2653-031 | An error occurred while querying package name. |
Explanation: Could not check if package is installed.
User Response: If CSM failed to install properly during a full install, try issuing the updatenode command to install CSM.
2653-032 | Could not mount file system that could not be mounted. |
Explanation: Either the mkdir command or the mount command failed.
User Response: Check the previous error message to see which command failed, and perform diagnostics for that command.
2653-033 | Could not unmount file system that could not be mounted. |
Explanation: The unmount command failed.
User Response: Try to unmount /csminstall on the remote node using dsh.
2653-034 | Could not remove command to remove from place to remove if from. |
Explanation: Could not remove csmfirstboot from /etc/inittab.
User Response: Try editing /etc/inittab directly.
2653-035 | Could not find file. |
Explanation: The specified object does not exist.
User Response: Determine why the object does not exist, create it, and then try the command again.
2653-036 | Could not update object not updated. |
Explanation: Could not update /etc/inittab.
User Response: Check /etc/inittab on the remote node.
2653-037 | The internal call to command that was called was not successful. |
Explanation: Internal called unmount was not successful.
User Response: Try running unmount directly on the remote node using dsh.
2653-038 | Could not process command arguments. |
Explanation: None.
User Response: None.
2653-043 | file that does not exist does not exist. |
Explanation: None.
User Response: None.
2653-044 | Could not remove file or directory name. |
Explanation: The rm command failed.
User Response: Check for the existence of the specified file, and try to remove it manually.
2653-045 | Could not write to file file name. |
Explanation: Could not open /etc/inittab.tmp for writing.
User Response: If CSM failed to install properly during a full install, try issuing the updatenode command to install CSM.
2653-046 | csm.core package is not installed. Please install csm.core package first. |
Explanation: In order to install the management server using the installms command, the csm.core package needs to be installed first.
User Response: Install the csm.core package.
2653-048 | Command failed: command that failed. Error message: error message. |
Explanation: A command that was called by program name had a failure while it was running.
User Response: None.
2653-049 | Invalid argument to run_cmd subroutine: runtype (like show_errors, ignore error). |
Explanation: The run_cmd subroutine was called with invalid arguments.
User Response: Call the run_cmd subroutine with the necessary arguments.
2653-050 | Linux distribution, distribution name, is not currently supported by CSM. Supported distributions are: list of supported Linux distribution names. |
Explanation: The system on which you are installing CSM does not have a supported Linux distribution.
User Response: Install CSM on a supported Linux distribution.
2653-051 | rpm command package is not installed. Please install rpm command package first to get the rpm command. |
Explanation: The package or installp image that has the rpm command is not installed on the system.
User Response: Install the rpm.rte package.
2653-052 | Trouble comparing version and release numbers that are being compared. Eval message: Eval message. |
Explanation: None.
User Response: None.
2653-053 | Cannot find a version of the rpm name rpm with the condition operator (like>=)rpm version, rpm name. (This is required by first rpm is required to install second rpm). |
Explanation: None.
User Response: None.
2653-054 | Improper attr=value form. |
Explanation: The attribute=value operands provided on the command line were not correct. There might be a missing equals (=) sign, or a flag might have been mistaken for an attribute. All flags must come before the attributes on the command line.
User Response: Check the command's man page for the correct syntax and then rerun the command.
2653-055 | Invalid attribute: attribute. |
Explanation: The attribute provided on the command line is not a valid attribute for this command. See the nodeattributes man page for the list of valid attributes.
User Response: Check the command's man page for the correct syntax and then rerun the command.
2653-056 | Cannot provide -c, -C, -H, -m, or -n with -f. |
Explanation: The combination of flags provided on the command line cannot be used together. If a nodedef file name is provided via the -f flag, then the flags listed in the the message cannot be provided.
User Response: Check the command's man page for the correct syntax and then rerun the command.
2653-057 | Cannot provide -c, -f, -H, -n or the HWControlPoint, HWControlNodeId or PowerMethod attributes with -M. |
Explanation: The combination of attributes and flags provided on the command line cannot be used together. If the -M flag is provided, the flags and attributes listed in the message cannot be provided.
User Response: Check the command's man page for the correct syntax and then rerun the command.
2653-058 | PowerMethod attribute must be provided when using the -H flags. |
Explanation: The -H flag defines the hardware control attributes of a node. Hardware control requires that the PowerMethod attribute is set correctly.
User Response: Rerun the command with both the -H flag and the PowerMethod=attribute.
2653-059 | ConsoleMethod attribute must be provided when using -C flag. |
Explanation: The -C flag defines the remote console attributes of a node. Remote console requires that the ConsoleMethod attribute is set correctly.
User Response: Rerun the command with both the -C flag and the ConsoleMethod=value attribute.
2653-060 | There is no group with name node group name. |
Explanation: None.
User Response: None.
2653-061 | Cannot determine the operating system name on the Management Server. |
Explanation: There was a problem determining the running operating system, probably because it is not Linux.
User Response: Ensure that you are running a supported operating system.
2653-062 | Cannot determine the version of the distribution installed on the Management Server. |
Explanation: There was a problem determining the version of the running operating system, probably because it is not Linux. On Linux, this version is taken from the /etc/redhat-release file.
User Response: Ensure that you are running a supported operating system.
2653-063 | Cannot determine the name of the distribution installed on the Management server. |
Explanation: There was a problem determining the name of the distribution of the running operating system, probably because it is not Linux. On Linux, this version is taken from the /etc/redhat-release file.
User Response: Ensure that you are running a supported operating system.
2653-064 | Cannot determine the architecture of the Management Server. |
Explanation: There was a problem determining the architecture of the machine. Probably because the machine is not running Linux . On Linux, the name command is run to obtain the architecture.
User Response: Ensure that you are running a supported operating system.
2653-065 | Cannot determine the CSM version installed on the Management Server. |
Explanation: There was a problem determining the version of csm.core that is installed on the system.
User Response: Ensure that there are no problems with the installation of csm.core.
2653-066 | The following nodes are already defined as ManagedNodes: space-separated list of nodes. |
Explanation: Nodes that are already defined cannot be redefined.
User Response: Rerun the command with a different set of nodes.
2653-068 | The starting console port number port number must be a hexadecimal digit. |
Explanation: If an esp console server is used, the port numbers are in hexadecimal format.
User Response: Rerun the program with the console port number value in hexadecimal format.
2653-069 | The following requested ports for console server console server name are already assigned to existing nodes:space-separated list of console port numbers in use. |
Explanation: Each console port for a console server can only be assigned to one node.
User Response: Rerun the program and specify a different set of console port numbers.
2653-070 | number of nodes nodes were specified, but only number of console ports console ports are available. |
Explanation: There must be enough console ports specified to accommodate all the nodes.
User Response: Rerun the command and specify more console ports. Additional console severs may be needed to provide enough console
2653-071 | number of nodes nodes were specified, but only number of service processors service processors are available. |
Explanation: There must be enough service processors specified to accommodate all the nodes.
User Response: Rerun the command and specify more service processors. Additional hardware control points may be needed to provide enough service processors for all the nodes.
2653-072 | Cannot run command name. |
Explanation: There was a problem when program name tried to run an external command.
User Response: See the error messages from the external command.
2653-073 | Cannot execute RMC command: RMC command. Error message from RMC: error message. |
Explanation: None.
User Response: None.
2653-074 | File not found: filename. |
Explanation: A file that program name was expecting does not exist.
User Response: Create the file and rerun the program.
2653-075 | The nodedef file has an invalid format on line line number. No hostname for the contents of a line in the nodedef file. |
Explanation: A line in the nodedef file has a format that cannot be understood. See the nodedef man page for details on the nodedef file format.
User Response: Fix the format of the nodedef file and rerun the definenode command.
2653-076 | The nodedef file has an invalid attribute on line line number: attribute name. |
Explanation: Only valid attributes may be specified in the nodedef file. See the nodeattributes man page for the list of valid attributes.
User Response: Fix the attribute name in the nodedef file and rerun the definenode command.
2653-077 | Errors in nodedef file: filename. |
Explanation: There were some errors in the nodedef file. See the message that were displayed before this message for details.
User Response: Fix the nodedef file and rerun the definenode command.
2653-078 | Nodes are already defined. |
Explanation: Some nodes were already defined, and cannot be redefined. See the messages that were displayed before this message for details.
User Response: Rerun the command and specify a different set of nodes.
2653-079 | Cannot assign install method to nodes. |
Explanation: None.
User Response: None.
2653-080 | Cannot assign console ports to nodes. |
Explanation: Some nodes could not have console ports assigned to them. See the messages that were displayed before this message for details.
User Response: Rerun the command and specify either a different set of nodes or a different set of console ports.
2653-081 | Cannot assign service processors to nodes. |
Explanation: Some nodes could not have service processors assigned to them. See the messages that were displayed before this message for details.
User Response: Rerun the command and specify either a different set of nodes or a different set of service processors.
2653-082 | No nodes were successfully defined. |
Explanation: None.
User Response: None.
2653-083 | Nodes were successfully defined, but there was an error installing the nodes. |
Explanation: Since the -U flag was provided, the definenode command attempted to run the updatenode command on the nodes. This message appears if there is a failure in the updatenode command.
User Response: See the error messages from the updatenode command.
2653-084 | Could not get the list of install packages. |
Explanation: None.
User Response: If CSM failed to install properly during a full install, try issuing the updatenode command to install CSM.
2653-085 | An error occurred while checking CSM packages. |
Explanation: The command was not able to test the install of the required packages.
User Response: Check the previous error messages to determine the cause of the problem.
2653-086 | The -f flag cannot be used with the -t flag. |
Explanation: Usage error.
User Response: Do not specify both the -f and -t flags with the updatenode command.
2653-088 | CSM distribution, CSM distribution version, is not currently supported. Supported distributions are: list of supported CSM distributions. |
Explanation: The system on which you are installing CSM does not have a supported CSM distribution version.
User Response: Install CSM on a system that has a supported CSM distribution version.
2653-089 | IP address ip address out of valid range. |
Explanation: None.
User Response: None.
2653-090 | The /etc/dhcpd.conf file does not look correct. The line ### CSM STATIC ENTRIES in /etc/dhcpd.conf file could not be found. Please run createdhcp first, and then updatedhcp. |
Explanation: The /etc/dhcpd.conf file has been changed so that the program cannot do any file editing. Most likely, createdhcp was never run.
User Response: Run the csmsetupks command (which runs createdhcp and updatedhcp).
2653-091 | The MAC address for ip address of node that was not defined was not defined. |
Explanation: Could not get the MAC address.
User Response: After checking your network, try to get the MAC address again.
2653-092 | Node node name does not have a valid install method. The valid install methods are: list of valid installation methods. |
Explanation: None.
User Response: None.
2653-093 | Could not find the following prerequisite RPMs: list of requisite rpms not found. |
Explanation: Cannot find the prerequisites on the CD or in the given path.
User Response: Rerun the command with the path that contains the file.
2653-094 | ERRM did not start -- continuing install of CSM anyway. |
Explanation: None.
User Response: None.
2653-095 | All nodes must have the same value for the attribute name attribute. |
Explanation: None.
User Response: None.
2653-096 | The attribute name attribute is not set for any of the nodes. |
Explanation: None.
User Response: None.
2653-097 | Invalid value for Mode attribute: mode attribute. Valid Mode attributes are: list of valid Mode attributes. |
Explanation: None.
User Response: None.
2653-098 | Could not get MAC address for node name. |
Explanation: Could not get the MAC address via the getmacs command.
User Response: Run the program again and check configurations atftp, nfs, and console server.
2653-100 | Node node name failed to reboot. |
Explanation: The node would not reboot.
User Response: Check that rpower works correctly.
2653-101 | There are no valid nodes given. |
Explanation: The program was not given any nodes for which to get MAC addresses.
User Response: None.
2653-102 | Could not get required information from file name. |
Explanation: Could not find /etc/niminfo file.
User Response: Determine why /etc/niminfo was not created by NIM.
2653-103 | Could not get management server and node hostname. |
Explanation: The command could not find the information it needed.
User Response: If CSM was not installed successfully during a full install of a node, run the updatenode command to complete the CSM installation of the node.
2653-104 | Could not get node attribute values from config_info file. |
Explanation: The command could not get the required information from the node's configuration information file (/csminstall/csm/config/hostname.configinfo).
User Response: If CSM was not installed successfully during a full install of a node, run the updatenode command to complete the CSM installation of the node.
2653-105 | An error occurred when copying files to directory name. |
Explanation: An error occurred when attempting to copy files to the /opt/csm/install directory.
User Response: If CSM was not installed successfully during a full install of a node, run the updatenode command to complete the CSM installation of the node.
2653-106 | Could not open name of file. |
Explanation: The open command failed.
User Response: If CSM was not installed successfully during a full install of a node, run the updatenode command to complete the CSM installation of the node.
2653-108 | Cannot open file to add remote console lines. |
Explanation: None.
User Response: None.
2653-109 | An error occurred when attempting to execute command that produced the error. |
Explanation: Could not execute the makenode command.
User Response: Examine the /var/log/csm/install.log file on the remote node to determine why the command failed.
2653-110 | There is no target for the installnode command. Please specify a target with the -a, -P, -N or hostname positional arguments. |
Explanation: At least one node must be specified.
User Response: Rerun the command with the -a, -P, -N, or hostnames flag.
2653-111 | The following nodes have an unsupported InstallMethod:comma-separated list of nodes. |
Explanation: The only supported InstallMethod is kickstart. This should have been set when the csmsetupks command was run.
User Response: Run the csmsetupks command, and then run the installnode command again.
2653-112 | Error starting service name service. |
Explanation: A service could not be started. See the message that were displayed before this message for details.
User Response: Start the service manually and then rerun the installnode command.
2653-113 | Mode can only be set to PreManaged, Installing, or Managed. |
Explanation: This is an internal error and is only displayed if there is an error in installnode.
User Response: Contact IBM service or send a note to cluster@us.ibm.com.
2653-115 | Not installing node node name. |
Explanation: None.
User Response: None.
2653-116 | Error running csmsetupks. |
Explanation: There was an error when csmsetupks was run that prevents installnode from running.
User Response: If it was not run previously, run the csmsetupks command. If the csmsetupks command has already been run, look for errors in /var/log/csm/csmsetupks.log. After csmsetupks has run successfully, run the installnode command again.
2653-117 | Error setting up /tftboot/pxelinux/pxe files. |
Explanation: The /tftpboot/pxelinux.cfg directory could not be created.
User Response: Check the permissions and disk space, and then rerun the installnode command.
2653-118 | Cannot change the mode of filename or directory to mode. |
Explanation: A filename or directory's mode could not be changed with the chmod command.
User Response: Check the permissions of the directory and then rerun the command.
2653-119 | Cannot create file filename. |
Explanation: A file could not be created.
User Response: Check the permissions and disk space, and then rerun the command.
2653-120 | Cannot copy file to be copied to destination directory. |
Explanation: None.
User Response: None.
2653-121 | Node node name is not statically defined in dhcp configuration filename (/etc/dhcp.conf). |
Explanation: The node does not appear in a static stanza in the /etc/dhcpd.conf file. This is probably due to an error while running the csmsetupks command.
User Response: Look at the log file for csmsetupks (/var/log/csm/csmsetupks.log) and then, when the csmsetupks problems have been fixed, rerun the installnode command.
2653-122 | The following nodes had missing files: newline-separated list of node names. |
Explanation: Files were not created or updated by csmsetupks.
User Response: Check for errors in the csmsetupks log (/var/log/csm/csmsetupks.log). Once csmsetupks runs successfully, rerun the installnode command.
2653-123 | filename was not copied to /csminstall by installms or copycsmpkgs. |
Explanation: installms or copycsmpkgs should have copied this file into the /csminstall tree.
User Response: Rerun installms or copycsmpkgs with the correct path and attributes, and then rerun the installnode command.
2653-124 | Files are missing from /csminstall/csm. |
Explanation: Certain files should have been copied to /csminstall/csm by installnode or copycsmpkgs, but those files are not in the directories.
User Response: Rerun installms or copycsmpkgs with the correct path and attributes, and then rerun the installnode command.
2653-125 | Cannot start tftp daemon. |
Explanation: The tfpt daemon cannot be started.
User Response: See the messages that were displayed before this message for details.
2653-126 | Cannot start dhcp daemon. |
Explanation: The dhcp daemon cannot be started.
User Response: See the messages that were displayed before this message for details.
2653-127 | The following nodes had a problem installing: newline-separated list of nodes. |
Explanation: This is a summary of all the nodes that had problems when the installnode command was run.
User Response: Fix the problems (described in the messages that were displayed before this message), and then rerun the installnode command on the nodes that failed.
2653-128 | Error initializing the status directory or status file. |
Explanation: The /csminstall/csm/status directory (with a symbolic link to /tftpboot/status) could not be created, or a node's status file could not be created in that directory
User Response: Check the permissions and disk space, and then rerun the installnode command.
2653-129 | No node defined. Error in program. |
Explanation: None.
User Response: None.
2653-130 | Invalid cfm option: invalid flag |
Explanation: You passed an invalid flag to --cfmoptions.
User Response: Pass only flags that are designated by the updatenode -h command to --cfmoptions.
2653-131 | package name prerequisite : prerequisite name is not installed. |
Explanation: None.
User Response: None.
2653-132 | No Console Methods are defined in the system. At least one Console Method should be defined in /opt/csm/bin/*_console. |
Explanation: There are no valid console methods. Remote console is not supported on this system.
User Response: Ensure that the csm.server package was properly installed.
2653-133 | No Power Methods are defined in the system. At least one Power Method should be defined in /opt/csm/bin/*_power or /opt/csm/lib directory. |
Explanation: There are no valid power methods. Hardware control is not supported on this system.
User Response: Ensure that the csm.server package was properly installed.
2653-134 | console method attribute is not a valid ConsoleMethod. The valid console methods are comma-separated list of valid console methods. |
Explanation: Only valid console methods may be specified with the ConsoleMethod=attribute.
User Response: Rerun the command using one of the valid console methods listed in the message
2653-135 | power method attribute is not a valid Power Method. The valid power methods are comma-separated list of valid power methods. |
Explanation: Only valid power methods may be specified with the PowerMethod=attribute.
User Response: Rerun the command using one of the valid power methods listed in the message
2653-136 | Required attribute values were not found in the configuration information file for node node name. |
Explanation: When the CSM installation scripts are executed on a cluster node, they need to get information from a configuration file in order to determine what to install on the node.
User Response: Check the configuration information file for this node which is stored in the /csminstall/csm/config directory. Make sure there are valid values for the attributes.
2653-137 | The file or directory name directory is missing. this probably means that xinetd is not installed. |
Explanation: None.
User Response: None.
2653-138 | Error: /install exists and is not a directory or an NFS mount point. Please remove the /install file. It is needed as a mount point for smsupdatenode. |
Explanation: None.
User Response: None.
2653-139 | Error: The directory /install exists, is not a mount point, and contains files. Please remove this directory. It is needed as a mount point for smsupdatenode. |
Explanation: None.
User Response: None.
2653-140 | Error: Command command name failed with return code return code (integer). |
Explanation: None.
User Response: Try running the command manually to diagnose the problem.
2653-141 | Cannot open file file name for writing. |
Explanation: The file does not have write access.
User Response: Ensure the file has write permission for root and that there is enough disk space.
2653-142 | Cannot open file file name for reading. |
Explanation: The file does not have read access.
User Response: Change the permissions of the file so that root has read access.
2653-143 | There is no target for the updatenode command. Please specify a target with the -a, -P, -M, -N, or hostname positional arguments. |
Explanation: Usage error.
User Response: Check the command usage and try issuing the command again.
2653-144 | Error running command name of the command. Reported return code (integer) |
Explanation: None.
User Response: None.
2653-146 | Error: Cannot open file file name to lock. Reported return code. |
Explanation: Could not open a file for exclusive locking.
User Response: Ensure no other process is using the file, and that the file permissions allow updatenode to open the file.
2653-147 | Another execution of updatenode may be running. Cannot place lock on file file name:return code |
Explanation: Could not get lock on file. Another process of updatenode may be running.
User Response: Wait until the other updatenode process has completed, and then run the updatenode command.
2653-148 | Error: CFM cannot be run to nodes whose Mode is Premanaged. |
Explanation: Usage error.
User Response: If you want to run CFM to a node whose Mode is Premanaged, you must install CSM on the node first. Run the updatenode -PIF command.
2653-149 | An error occurred when setting up CSM installation and configuration files. |
Explanation: Some part of the setup that was required on the management server did not complete successfully.
User Response: Check the previous message to determine the specific problem.
2653-150 | An error occurred when attempting to start NFS. |
Explanation: None.
User Response: Check the previous message to determine the problem.
2653-151 | An error occurred when attempting to export /csminstall. |
Explanation: None.
User Response: Check the previous message to determine the problem.
2653-152 | An error occurred when attempting to execute DSH. |
Explanation: The dsh command failed.
User Response: Try running the dsh command directly on the node to diagnose the problem.
2653-153 | Could not create configuration information files. |
Explanation: Configuration information files need to be created in /csminstall/csm/config to provide information to the node during installation.
User Response: Check the permissions and disk space, and then rerun the command.
2653-154 | Could not create node name mapping file. |
Explanation: Could not create the /csminstall/csm/config/nodemap file.
User Response: Check the previous message to determine the problem.
2653-155 | Could not find updatenode.client script. |
Explanation: The /csminstall/csm/updatenode.client file does not exist and could not be copied from /opt/csm/csmbin.
User Response: Make sure this script is copied to /csminstall/csm and try issuing the command again.
2653-156 | Could not get hostname as known by the management server. |
Explanation: The node's host name could not be found in the/csminstall/csm/config/nodemap file.
User Response: Ensure that the file exists.
2653-157 | Could not get node attribute values from the node config_info file. |
Explanation: None.
User Response: Check previous messages to determine why the file could not be read.
2653-158 | Could not create directory name directory. |
Explanation: The mkdir command file.
User Response: Try running the mkdir command directly to diagnose the problem.
2653-159 | Could not copy the original file file to destination file. |
Explanation: The copy command failed.
User Response: If CSM failed to install properly during a full install, try issuing the updatenode command to install CSM.
2653-160 | The following nodes are not defined: comma-separated list of nodes. |
Explanation: Shows the list of nodes that were not successfully defined.
User Response: Fix the problems (listed above) and run the definenode command again to define the nodes that were not defined.
2653-161 | Cannot use -x with -p option. |
Explanation: The -x flag and -p flag should not be used together. The -x flag specifies not to copy packages, while the-p flag specifies to copy them from a path.
User Response: Rerun the program and specify-x or-p, but not both -x and -p.
2653-162 | eth0 not up and running on Management Server. |
Explanation: None.
User Response: None.
2653-163 | There is no target for the csmsetupks command. Please specify a target with the -a, -P, -N or -n flags. |
Explanation: At least one node must be specified.
User Response: Rerun the command with one of the following flags: a, -P, -N, -n.
2653-164 | Cannot copy source file name to target filename. return code. |
Explanation: There was a problem copying a file.
User Response: Check the permissions and disk space, and then rerun the command.
2653-165 | Skipping pathname. This directory does not look like it contains the contents of a Red Hat CD-ROM. |
Explanation: csmsetupks attempts to verify that a directory contains a copy of the Red Hat CD-ROMs. The directory must contain the Red Hat/RPMS subdirectory, in which the RPMs are stored.
User Response: Check that the path is correct, and then rerun the command.
2653-166 | None of the directories had anything to copy (PKGPATH= colon-separated list of pathnames). |
Explanation: Nothing was copied. Either all the directories were empty, or none of them looked like Red Hat CD-ROMs.
User Response: Check that the path is correct, and the rerun the command.
2653-167 | Error while copying the Red Hat images. |
Explanation: The Red Hat packages could not be copied.
User Response: Make sure the path is correct and you have enough disk space to hold all the images. You need about 1.5GB to hold the contents of both Red Hat disks.
2653-168 | Error setting up PXE. |
Explanation: The /tftpboot/pxelinux.cfg directory could not be created.
User Response: Check the permissions and disk space, and then rerun the csmsetupks command.
2653-169 | Error getting MAC addresses. |
Explanation: The MAC addresses of one or more nodes could not be obtained, either through dsh, or by running the getmacs command.
User Response: See the messages that were displayed before this message for details. Rerun the csmsetupks command to attempt to get the MAC addresses of the nodes again.
2653-170 | Error setting up Kickstart configuration file. |
Explanation: One or more of the following failures could have occurred:
User Response: Ensure that the path provided with the -p flag contains a full copy of the Red Hat CD-ROMs. Ensure the kickstart template file exists and is in the correct format. Rerun the csmsetupks command after fixing the problems.
2653-171 | Error running updatedhcp. |
Explanation: Could not add static node stanzas to the /etc/dhcpd.conf file.
User Response: See the messages that were displayed before this message for details. Rerun the csmsetupks command to get the nodes added to the /etc/dhcpd.conf file.
2653-172 | Error setting InstallMethod attribute to "kickstart". |
Explanation: The InstallMethod attribute for one or more managed nodes could not be set to kickstart. If the attribute is not set to kickstart, then the installnode command will not allow the node to be installed.
User Response: Try setting the InstallMethod to kickstart manually using the chnode command. If this works, there is no need to rerun the csmsetupks command.
2653-173 | The IP address of node node name is not found in the /etc/dhcpd.conf file. |
Explanation: You tried to run the getmacs command without running the createdhcp command first.
User Response: Make sure the node is defined, and then run the createdhcp command. Check the /etc/dhcpd.conf file and make sure there is an entry with the IP address of this node included in a range.
2653-174 | Could not find attribute values in file name file. |
Explanation: The required attribute values were not found in the file.
User Response: If CSM failed to install properly during a full install, try issuing the updatenode command to install CSM.
2653-175 | No nodes provided. |
Explanation: No nodes were provided to the definenode command.
User Response: Rerun the command with the -n flag.
2653-176 | The program was terminated by the user. |
Explanation: The program was unexpectedly interrupted by the user.
User Response: Run the program again.
2653-177 | Cannot assign the same attribute name to more than one node. |
Explanation: Some attributes can only be applied to a single node at a time because multiple nodes cannot have the same value for these attributes.
User Response: Rerun the command and only specify a single node to define.
2653-178 | Cannot provide ConsolePortNum, ConsoleServerNumber, or ConsoleServerName attributes with -C. |
Explanation: The -C flag sets the node's ConsolePortNum, ConsoleServerNumber and ConsoleServerName attributes automatically, so these attributes should not be provided with the -C flag.
User Response: Run the command again and do not provide the listed attributes with the -C flag.
2653-179 | Cannot provide HWControlPoint attribute with -H. |
Explanation: The -H flag sets the node's HWControlPoint attribute automatically, so HWControlPoint should not be provided with the-H flag.
User Response: Rerun the command and do not provide both the HWControlPoint attribute and the -H flag together.
2653-180 | Cannot delete directory or file file or directory name. |
Explanation: None.
User Response: None.
2653-181 | Cannot erase rpm package rpm package name. |
Explanation: None.
User Response: None.
2653-182 | Cannot uninstall installp package install package name. |
Explanation: None.
User Response: None.
2653-183 | The hostname map file has no hostname on line line number. |
Explanation: None.
User Response: Add the host name to each line of the hostname map file, and then rerun the definenode command.
2653-184 | Errors in hostname map file: filename. |
Explanation: This message appears after more detailed messages have already been displayed. Refer to the prior messages for details.
User Response: Fix the errors in the hostname map file and rerun the definenode command.
2653-185 | Could not get the CSM version from the system. Please supply the valid CSM version attribute value or please install csm.core package first. |
Explanation: None.
User Response: None.
2653-186 | Cannot extract the file name from rpm or package name. |
Explanation: None.
User Response: None.
2653-187 | The /etc/dhcpd.conf file can no longer be modified by createdhcp. You should manually go fix the changes you want to make with the Netmask, the Gateway, or the Name servers. |
Explanation: The /etc/dhcpd.conf file can no longer be parsed, because of the way the program has been set up. This probably means that you modified the lines in the /etc/dhcpd.conf file where they shouldn't have been modified. It could also mean that you have simply changed the file too extensively for our script to recognize.
User Response: Save the /etc/dhcpd.conf file to a temporary directory and then erase /etc/dhcpd.conf. Next, run the program again. It will create a new /etc/dhcpd.conf file, which you can modify with your own settings.
2653-188 | Skipping to the next valid header. |
Explanation: An error was found in a node definition stanza contained in a node definition file. The definenode command will skip to the next valid stanza header.
User Response: Correct the error in the node definition file and check the related node definition for accuracy.
2653-189 | Node node name appears in multiple stanzas. It will not be defined. |
Explanation: Multiple stanzas for the same node definition were found in the node definition file.
User Response: Edit the node definition file to remove extra stanzas.
2653-190 | The Management Server attribute on the node is different from the Management Server attribute from the management server. |
Explanation: None.
User Response: None.
2653-191 | Cannot remove the members of the node group. |
Explanation: None.
User Response: None.
2653-192 | Cannot remove node group from the system. |
Explanation: None.
User Response: None.
2653-193 | Cannot use the -a flag together with the -N flag. |
Explanation: The -a indicates all groups and the -N is used to specify a list of group names.
User Response: Chose either the -a flag or the -N flag, and then rerun the command.
2653-195 | Either the -a or -N flag must be specified. |
Explanation: This command requires that either the -a or -N flag be specified.
User Response: Check the command usage and then rerun the command.
2653-196 | An invalid format was used on the command line. |
Explanation: Invalid format was used on the command line.
User Response: Check the command usage and then rerun the command.
2653-198 | An invalid group name group name was provided on the command line. |
Explanation: A group name provided on the command line was not a valid CSM group.
User Response: Check for valid groups and rerun the command.
2653-199 | Incorrect arguments were used when calling this command. |
Explanation: The arguments supported by this command were not used correctly.
User Response: Check the command usage and then rerun the command.
2653-200 | Either the cable_type or ring_speed must be provided. |
Explanation: This command requires that either the ring_speed or cable_type attributes be provided.
User Response: Check the command usage and then rerun the command.
2653-202 | An invalid value was specified for the attribute name attribute. |
Explanation: The value given for the specified attribute was not valid.
User Response: See the man page for the command, or CSM Commands, and then rerun the command.
2653-203 | The value of the attribute name attribute for node node name is missing. |
Explanation: The value for the specified attribute in the CSM node definition is not set.
User Response: Set the required attribute and then rerun the command.
2653-205 | There are no devices associated with subnet subnet (ip address). This implies that either the network is not configured -- or -- The incorrect netmask netmask (ip address) value was passed in. |
Explanation: None.
User Response: Check the network configuration.
2653-206 | dsh cannot connect to nodes: node names through protocol remote shell protocol. |
Explanation: None.
User Response: None.
2653-207 | directory name that need to created directory needs to be created. But a file exits with the same name. Move the file to another name and rerun the command. |
Explanation: None.
User Response: None.