| 0028-001 | Primary node not defined - use "Eprimary". |
Explanation: A primary node must be assigned before running Estart.
User Response: See the Eprimary command in PSSP: Command and Technical Reference for information on how to assign a primary node.
| 0028-002 | Cannot ping the primary node: primary node. |
Explanation: The primary node cannot be pinged.
User Response: See the chapter on diagnosing switch problems in PSSP: Diagnosis Guide for information on verifying the primary node.
| 0028-003 | Switch initialization failed on hostname - i_stub call error. |
Explanation: Internal error.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-004 | Switch initialization failed on hostname - insufficient memory. |
Explanation: Internal error.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-005 | Switch initialization failed on hostname - daemon busy. Retry command. |
Explanation: Fault service daemon is busy processing a request.
User Response: Retry command.
| 0028-006 | Switch initialization failed on hostname - i_stub problem. |
Explanation: Internal error.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-007 | Switch initialization limit second time limit exceeded. |
Explanation: Estart processing has exceeded allowable time limit.
User Response: See the chapter on diagnosing switch problems in PSSP: Diagnosis Guide.
| 0028-008 | Cannot access system data repository. |
Explanation: Cannot access system data repository.
User Response: See the chapter on diagnosing switch problems in PSSP: Diagnosis Guide.
| 0028-009 | You have specified an invalid number of arguments. |
Explanation: You have specified an incorrect number of arguments.
User Response: Check syntax and enter the command again.
| 0028-010 | The node identifier for primary/backup node node id could not be found in the repository. |
Explanation: The node you specified as primary is not valid.
User Response: Check the name of the node that you want to be the primary node.
| 0028-011 | You have specified an invalid starting frame number. |
Explanation: The starting frame number you specified is not valid.
User Response: Check that the frame number you specified is in your configuration.
| 0028-012 | You have specified an invalid starting slot number. |
Explanation: The starting slot you specified is out of range (1 to 16).
User Response: Specify a starting slot number in the valid range.
| 0028-013 | You have specified an invalid node count. |
Explanation: The number of nodes you specified is out of range.
User Response: Specify a number greater than zero and less than the number of maximum nodes.
| 0028-014 | Start node plus count must not exceed the maximum number of nodes. |
Explanation: The number specified is not a valid number.
User Response: Specify a number less than the maximum number of nodes.
| 0028-015 | The specified protocol is not valid. |
Explanation: You have specified a protocol which is not valid.
User Response: Enter the command again using the correct syntax.
| 0028-016 | Node to be changed could not be found in the repository. |
Explanation: The node you specified is not valid.
User Response: Check the name of the node for which you want to change the protocol and enter the command again.
| 0028-017 | Unable to store topology file in SDR. |
Explanation: SDRCreateFile was not successful storing the topology file.
User Response: Check that System Data Respository is operating correctly.
| 0028-018 | Unable to modify Switch_partition object in SDR. |
Explanation: SDRChangeAttrValues was not successful for Switch_partition object. (Switch partitions are not supported.)
User Response: Check that System Data Repository is operating correctly.
| 0028-019 | Unable to query Switch_partition object in SDR. |
Explanation: SDRGetObjects was not successful for Switch_partition object. (Switch partitions are not supported.)
User Response: Check that System Data Repository is operating correctly.
| 0028-020 | Unable to retrieve the topology file out of SDR. |
Explanation: Unable to retrieve the topology file out of the System Data Repository.
User Response: Check that the System Data Repository is operating correctly.
| 0028-021 | topology_file_name is not valid. |
Explanation: The specified topology file does not exist.
User Response: Check that the specified topology_file_name exists.
| 0028-022 | Unable to create Switch_partition object. |
Explanation: SDRCreateObjects was not successful for Switch_partition object.
User Response: Check that the System Data Repository is operating correctly.
| 0028-023 | fault_service_Worm_RTG daemon not running on primary node. |
Explanation: The fault_service_Worm_RTG daemon not running on primary node.
User Response: See the chapter on diagnosing switch problems in PSSP: Diagnosis Guide.
| 0028-024 | No reliable hostname defined for this node in SDR. |
Explanation: A reliable hostname is not defined for this node in SDR Node Object.
User Response: Define a reliable hostname for this node.
| 0028-025 | A primary or backup value in the Switch_partition is null or not valid. |
Explanation: One of the primary or backup values for the switch primary node is not valid and is probably null.
User Response: Set the primary or backup value with the Eprimary command.
| 0028-027 | Cannot ping the primary backup node, cannot Estart: node_name. |
Explanation: The oncoming primary backup node specified for the SP switch is not available.
User Response: Check the oncoming primary backup node and select another node if necessary.
| 0028-028 | Fault service worm not up on oncoming primary node, cannot Estart: node_name. |
Explanation: The worm daemon on the oncoming primary node is not available. This message may also be issued if Estart is unable to issue the remote command to the oncoming primary node.
User Response: Run rc.switch again on the oncoming primary node or use the Eprimary command to choose another node.
| 0028-029 | Fault service worm not up on oncoming primary backup node, cannot Estart: node_name. |
Explanation: The worm daemon on the oncoming primary backup node is not available.
User Response: Run rc.switch again on the oncoming primary backup node or use the Eprimary command to choose another node. If the problem is due to a remote command error, check the Kerberos authentication setup.
| 0028-030 | css0 IP driver failed to detach. |
Explanation: The css0 IP driver did not detach.
User Response: Issue the command again. If the problem persists, contact the IBM Support Center.
| 0028-031 | css0 unconfiguration method failed. |
Explanation: The css0 unconfiguration method was not successful.
User Response: Issue the command again. If the problem persists, contact the IBM Support Center.
| 0028-032 | css0 configuration method failed. |
Explanation: The css0 configuration method was not successful.
User Response: Issue the command again. If the problem persists, contact the IBM Support Center.
| 0028-033 | rc.switch failed. See /var/adm/SPlogs/css/rc.switch.log for more information. |
Explanation: The rc.switch was not successful. The worm daemon is not running.
User Response: Review /var/adm/SPlogs/css/rc.switch.log for more information.
| 0028-034 | Unable to delete existing topology file from SDR. Return code=SDRDeleteFile return code. |
Explanation: SDRDeleteFile issued a return code indicating a problem exists.
User Response: Check the meaning of the System Data Repository return code and take the appropriate action.
| 0028-035 | Oncoming primary node is fenced, cannot Estart: node_name. |
Explanation: The oncoming primary node that Estart uses is fenced.
User Response: Check the node. Use the Eprimary command to select another oncoming primary node, if necessary.
| 0028-036 | No functional switch primary node, run Estart. |
Explanation: There is no node running as the primary. This is the initial state of the system, or the state when rc.switch is run on the current primary node. This state also occurs when a primary node is taking over control.
User Response: Use the Eprimary command for additional information. If necessary, run the Estart command.
| 0028-037 | The switch partition is not valid. |
Explanation: The SP_NAME shell variable is not set to a valid system partition name.
User Response: Set the SP_NAME shell variable and then issue the command again.
| 0028-038 | Note: Oncoming primary node is fenced primary node name. |
Explanation: The oncoming primary node that the Estart command uses is fenced.
User Response: Make sure that the oncoming primary node is not fenced before the Estart command uses it.
| 0028-039 | Note: Fault service worm not up on oncoming primary node: primary node name. |
Explanation: The worm daemon on the oncoming primary node is not available.
User Response: Make sure that the oncoming primary node is available before the Estart command uses it.
| 0028-040 | Note: Oncoming primary backup node is fenced. |
Explanation: The oncoming primary backup node is fenced off.
User Response: Make sure that the oncoming primary backup node is not fenced before Estart uses it.
| 0028-041 | Oncoming primary and oncoming primary backup cannot be the same node. |
Explanation: The nodes specified on the command line for oncoming primary and oncoming backup primary are the same. The oncoming primary and oncoming primary backup cannot be the same node.
User Response: Select either another primary node or primary backup node.
| 0028-042 | Cannot change personality on node node_name. |
Explanation: The personality of the specified primary or backup node cannot be changed to that of a secondary node. Either the node is unreachable using the remote command, or the fault service worm daemon is not running on the node.
User Response: The Estart or Equiesce command continues. If an Estart command was issued, the node may be fenced if the worm daemon is down. Start the worm daemon on the node and issue Eunfence. If the problem is due to a remote command error, check the Kerberos authentication setup.
| 0028-043 | Primary backup node node_name busy. Retry command later. |
Explanation: The daemon would not accept the change personality command because the primary backup node is busy. Either a primary or backup primary node takeover is occurring.
User Response: The Estart or Equiesce was not successful. Issue the command again later.
| 0028-044 | Unable to find suitable primary backup node. No primary backup node running. |
Explanation: The oncoming primary backup node in the System Data Repository was not available. Either the Ethernet is down, the daemon is not running, or the primary backup node is fenced. The switch attempted to choose another node, but was not able to find an available node. The switch is running on the primary node.
User Response: Estart continues. Make sure that you intend to run only on the one node. If the reason a primary backup node could not be assigned is because the nodes are fenced, run Eunfence to unfence one or more nodes and then issue Estart again.
| 0028-045 | Expected.top file contains nodes outside the current partition, cannot start switch. |
Explanation: The expected.top file resides in /etc/SP on the primary node.
User Response: Estart continues. Make sure that you intend to run on only the one node.
| 0028-046 | Cannot ping the primary backup node: primary_backup_node. |
Explanation: The primary backup node cannot be pinged.
User Response: For information on verifying the primary node, see the chapter on diagnosing switch problems in PSSP: Diagnosis Guide.
| 0028-047 | Note: Fault service worm not up on oncoming primary backup node: primary backup node name. |
Explanation: The worm daemon on the oncoming primary backup node is not available.
User Response: Make sure that the worm daemon is available before Estart uses it.
| 0028-048 | Primary node node namebusy. Retry command later. |
Explanation: The daemon would not accept the change personality command because the primary node is busy. Either a primary or backup primary node takeover is occurring.
User Response: The Estart or Equiesce command was not successful. Issue the command again later.
| 0028-049 | Command not valid on switchless system. |
Explanation: This command is used to manage the switch and is, therefore, only valid on a system with a switch installed.
User Response: Issue the command only on systems with a switch installed.
| 0028-050 | The combination of command arguments is not valid. |
Explanation: You have specified an incorrect combination of command arguments.
User Response: Check syntax and enter the command again.
| 0028-051 | You have specified an incorrect switch number. |
Explanation: The switch number that you have specified is out of range.
User Response: Correct the switch number and enter the command again.
| 0028-052 | You have specified an incorrect switch clock input. |
Explanation: The switch number that you have specified is out of range (0 to 3).
User Response: Correct the switch clock input value and enter the command again.
| 0028-053 | Issuing the command command gave a return code of return code. |
Explanation: The Eclock command error was due to the error of the command used by Eclock.
User Response: Check the return code of the failing command and follow those actions; when complete, retry the Eclock command.
| 0028-054 | The switch number switch number is currently not powered on. |
Explanation: The switch switch number is not powered on, so the requested action was not completed.
User Response: Power on the switch and issue the command again.
| 0028-055 | Topology file contains an incorrect number of switch clock input statements. |
Explanation: The topology file you specified does not match the current SP configuration.
User Response: Select the correct topology file and issue the command again.
| 0028-056 | The switch number switch number clock input has changed to clock input, updating the System Data Repository (SDR). |
Explanation: The Error Logging daemon has detected a change in the clock input value for switch switch number, and has invoked a state change handler to reflect the new value in the System Data Repository.
User Response: None.
| 0028-057 | The switch number switch number has been powered-on. Setting the clock input value to clock input. |
Explanation: The Error Logging daemon has detected switch x being powered on, and has invoked a state change handler that sets the correct multiplexor (mux) value.
User Response: None.
| 0028-058 | You have specified an invalid switch number. |
Explanation: The switch number you specified is not valid.
User Response: Make sure that the switch number you specify is in your configuration.
| 0028-060 | Emonitor must be run from the control workstation. |
Explanation: The Emonitor command cannot be run from a node. Run it from the control workstation.
User Response: Issue the Emonitor command from the control workstation.
| 0028-061 | Estart is being issued to the primary node: primary node. |
Explanation: The Estart_sw command has been sent to the specified primary node via a remote command.
User Response: None.
| 0028-062 | The switch in frame frame number, slot slot number currently not receiving a clocking signal on the cable attached to jack number. |
Explanation: During Eclock command processing, it was discovered that one of the cables carrying the clocking signal is unplugged, missing, and/or damaged.
User Response: Check the cable specified in the message.
| 0028-063 | The System Data Repository (SDR) does not contain valid clock settings for the switch network. Reissue the command specifying a valid clock topology filename. |
Explanation: During Eclock command processing, it was discovered that the System Data Repository (SDR) does not contain valid clock settings for this switch. The Eclock -r command is valid only when a topology file has been previously specified.
User Response: Issue the Eclock command with the -f flag to specify a topology file.
| 0028-064 | The switch in frame frame number , slot jack number, is currently not receiving a clocking signal from its internal oscillator. |
Explanation: During Eclock command processing, it was discovered that one of the switch board oscillators is not functioning properly.
User Response: Check the specified cable.
| 0028-065 | The frame number frame number is currently not powered on. |
Explanation: During Eclock command processing, it was discovered that one of the frames in the SP Switch network is not powered on.
User Response: Check the specified frame.
| 0028-066 | The controller in frame number frame number is currently not responding. |
Explanation: During Eclock command processing it was discovered that one of the frame controllers is not responding.
User Response: Check the specified frame.
| 0028-067 | The node identifier specified is not eligible to be a Primary or Primary Backup node. |
Explanation: During Eprimary command processing, it has been determined that a dependent node has been specified either for the primary or the primary backup node. This is not allowed.
User Response: Check the specified node number and reissue the command using a standard SP node.
| 0028-068 | Unable to query Switch object in SDR. |
Explanation: An SDRGetObjects command did not succeed for Switch object.
User Response: Check that the System Data Repository is operating correctly.
| 0028-069 | Invalid clock alternate topology number alt_top_number specified. |
Explanation: The alternate topology number specified was greater than the number of switches in the system; or the alternate topology number was not found in the topology file.
User Response: Reissue the Eclock command using a correct alternate topology number and topology file name.
| 0028-070 | Unable to Estart, the clock source for one or more switch boards has changed. Eclock must be run to reestablish the clock distribution of the switch clock network. |
Explanation: The switch clock source has been changed to a value that may differ from what was set with the last Eclock command. This can cause a problem in a subsequent Estart commands if an Eclock command is not run prior to the Estart command.
User Response: Run the Eclock command then reissue the Estart command.
| 0028-071 | Switch initialization failed. The fault_service_Worm_RTG_SP daemon exited due to errors. See /var/adm/SPlogs/css/flt file for more information. |
Explanation: Switch initialization was not successful. The fault_service_Worm_RTG_SP daemon has encountered errors and has exited.
User Response: Review the /var/adm/SPlogs/css/flt file. See the chapter on diagnosing switch problems in PSSP: Diagnosis Guide.
| 0028-073 | Switch initialization ss second time limit exceeded. The fault_service_Worm_RTG_SP daemon is continuing to attempt to initialize the switch. See /var/adm/SPlogs/css/flt for more information. |
Explanation: Estart processing has exceeded the allowable time limit.
User Response: See the chapter on diagnosing switch problems in PSSP: Diagnosis Guide.
| 0028-075 | Could not distribute the topology file to these nodes. They may not come up on the switch network. |
Explanation: Estart attempted to distribute the switch topology file to all nodes with css adapters and host_responds=1 and was not successful on the listed nodes.
Probable causes are insufficient Kerberos authentication and lack of dasd space. These nodes may not have the proper topology file and therefore may not initialize on the switch.
User Response: Determine why the nodes could not receive the switch topology file then enter the command again.
| 0028-076 | The characteristics of the topology file on Node node does not appear to match that on CWS. |
Explanation: The Estart command attempted to distribute the topology to all nodes with adapters and host_responds=1 and was not successful on the specified nodes. These nodes may not have the proper topology file or the files have different characteristics.
User Response: Determine why the nodes could not receive the topology file. If the file is present, determine why the ls filename command returns different results. This may be due to different versions of the ls command or National Language Support considerations.
| 0028-077 | Switch initialization failed. The fault_service_Worm_RTG_CS daemon exited due to errors. See /var/adm/SPlogs/css0/p0/flt for more information. |
Explanation: Switch initialization was not successful. The fault_service_Worm_RTG_CS daemon has encountered errors and has exited.
User Response: Review the /var/adm/SPlogs/css0/p0/flt file. See the chapter on diagnosing switch problems in PSSP: Diagnosis Guide.
| 0028-078 | Switch initialization second time limit exceeded. The fault_service_Worm_RTG_CS daemon is continuing to attempt to initialize the switch. See /var/adm/SPlogs/css0/p0/flt for more information. |
Explanation: Estart processing has exceeded the allowable time limit.
User Response: See the chapter on diagnosing switch problems in PSSP: Diagnosis Guide.
| 0028-089 | Automatic unfence is not supported on a code_version primary node. |
Explanation: The user requested that automatic unfence be enabled or disabled, but the primary node does not support this feature.
User Response: The System Data Repository autounfence attribute is updated and Switch Initialization continues. However, the Fault Service daemon will ignore this attribute. Use the Eprimary and Estart commands to specify a primary node that supports automatic unfence.
| 0028-090 | Unable to modify the autounfence attribute of the Switch_partition object in the SDR. |
Explanation: The SDRChangeAttrValues command was not successful for the Switch_partition object.
User Response: Check that the System Data Repository is operating correctly and that the automatic unfence attribute (autounfence) is defined. If the message was issued by the Estart command, switch initialization continues.
| 0028-100 | Usage: --F input_file --f output_file --O [yes | no]. |
Explanation: The user did not specify all required parameters.
User Response: Specify the input file name and the output file name and enter the command again.
| 0028-101 | topology_filename does NOT exist, specify file name again. |
Explanation: The specified input file does not exist.
User Response: Verify the correct input file and enter the command again.
| 0028-102 | filename is NOT readable, specify file name again. |
Explanation: Specified input file is not readable.
User Response: Specify the input file name again.
| 0028-103 | Error on retrieving Switch Object from SDR. |
Explanation: The command SDRGetObjects Switch was not successful.
User Response: Check to see if the System Data Repository daemon, /usr/lpp/ssp/bin/sdrd, is running and if the object class Switch is defined.
| 0028-104 | Error on retrieving Node Object from the SDR. |
Explanation: The command SRGetObjects Node was not successful.
User Response: Check to see if the System Data Repository daemon, /usr/lpp/ssp/bin/sdrd, is running and if the object class Node is defined.
| 0028-105 | Error on retrieving topology_input_file from SDR. |
Explanation: Retrieval of the topology_input_file was not successful.
User Response: Check to see if the System Data Repository daemon /usr/lpp/ssp/bin/sdrd is running and if the specified topology input file is in the System Data Repository.
| 0028-106 | Error on saving topology_output_file to SDR. |
Explanation: Saving of the topology_output_file was not successful.
User Response: Check to see if the System Data Repository daemon /usr/lpp/ssp/bin/sdrd is running and check if the user has write permission to the System Data Repository.
| 0028-107 | Error on writing topology_output_file, check write permission. |
Explanation: Writing of the topology_output_file was not successful.
User Response: Check to see if the System Data Repository daemon /usr/lpp/ssp/bin/sdrd is running and check if the user has write permission on the specified directory.
| 0028-108 | Error return from Etopology. |
Explanation: The Etopology command was not successful.
User Response: Check to see if the correct file name was specified.
| 0028-109 | Output file was not saved, specify output file name and run again. |
Explanation: The output file name was not specified.
User Response: Specify the output file name.
| 0028-110 | Could not issue a remote command to the primary node due to authentication failure. |
Explanation: Kerberos authentication services rejected a remote command to the primary node.
User Response: Check the Kerberos authentication setup.
| 0028-111 | Could not issue a remote command to the primary backup node due to authentication failure. |
Explanation: Kerberos authentication services rejected a remote command to the primary backup node.
User Response: Check the Kerberos authentication setup.
| 0028-112 | Usage: Eannotator [-h] {-F input file|-d} --f output file --O {yes|no} [-p {0|all}] |
Explanation: You did not specify the required parameters.
User Response: Specify the input file name and the outfile name.
| 0028-113 | Usage: Eannotator --d option used only on SP_SWITCH2 or unpartitioned systems. |
Explanation: Specifying the --d option on a non SP_SWITCH2 system is not valid.
User Response: Specify the correct input file.
| 0028-114 | Error: Input file not a topology file. |
Explanation: The user specified an incorrect .top input file.
User Response: Specify the correct input file.
| 0028-115 | Error: Input file incorrect. Input nsbs: nsb(s) input System nsbs:nsbs in system |
Explanation: The user specified an incorrect .top input file.
User Response: Specify the correct input file.
| 0028-131 | Specify a number of days from 1 to 40. |
Explanation: The number of days specified is not valid.
User Response: Enter the command again using the correct syntax.
| 0028-132 | Specify the number of hours from 1 -- 23. |
Explanation: The number of hours specified is not valid.
User Response: Enter the command again using the correct syntax.
| 0028-133 | Specify the number of minutes, from 1 -- 59. |
Explanation: The number of minutes specified is not valid.
User Response: Enter the command again using the correct syntax.
| 0028-134 | Argument incorrect flag is not valid. |
Explanation: The argument specified is not valid.
User Response: Enter the command again using the correct syntax.
| 0028-135 | Run Phase Duration must not be greater than 40 days. |
Explanation: The time specified is too large.
User Response: Shorten the time specified to be less than or equal to 40 days.
| 0028-136 | IP address node_specifier was not found in the SDR. |
Explanation: Unable to find the IP address in the Adapter class of the System Data Repository.
User Response: Correct the problem with the System Data Repository.
| 0028-137 | Unable to find the Node class for Node number node_number in the SDR. |
Explanation: Unable to find information for this node.
User Response: Correct the problem with the System Data Repository.
| 0028-138 | Unable to find the Node class for frame frame_number and slot slot_number. |
Explanation: Unable to find information for this frame and slot number.
User Response: Correct the problem with the System Data Repository.
| 0028-139 | Incorrectly formed node specifier or incorrect option: node_specifier. |
Explanation: The node_specifier did not match one of the accepted forms.
User Response: Correct the problem with the System Data Repository.
| 0028-141 | No nodes specified. Type Eunfence -h for usage. |
Explanation: No nodes specified for this command.
User Response: Issue the command again. Make sure to specify nodes.
| 0028-142 | Topology file specified not valid for current partition. |
Explanation: Topology file does not match current partition.
User Response: Check to see which partition the user is running in and compare to the contents of the topology file.
| 0028-143 | Unable to retrieve the partition code level from the SDR. |
Explanation: Attempted to read code_level from Syspar class in the System Data Repository. The read was not successful.
User Response: Check to see if the System Data Repository daemon is running and that the Syspar class has not been corrupted.
| 0028-145 | Unable to retrieve information on Fenced nodes from the SDR. |
Explanation: Attempted to list the switch_responds class in the System Data Repository and received an error.
User Response: Check to see that the System Data Repository daemon is running and the repository has not been corrupted.
| 0028-146 | IP address node_specifier designates the Primary Node. The Primary node cannot be fenced or unfenced. |
Explanation: The IP address given belongs to the primary, which cannot be fenced or unfenced, because the primary is the node that does the fencing and unfencing.
User Response: Do not specify the primary node.
| 0028-147 | Node number node_number designates the Primary Node. The Primary node cannot be fenced or unfenced. |
Explanation: The node number given belongs to the primary, which cannot be fenced or unfenced, because the primary is the node that does the fencing and unfencing.
User Response: Do not specify the primary node.
| 0028-148 | Frame, Slot frame_number,slot_number designates the Primary Node. The Primary node cannot be fenced or unfenced. |
Explanation: The frame number and slot number given belongs to the primary, which cannot be fenced or unfenced, because the primary is the node that does the fencing and unfencing.
User Response: Do not specify the primary node.
| 0028-149 | Node name host_name designates the Primary Node. The Primary node cannot be fenced or unfenced. |
Explanation: The node name given belongs to the primary, which cannot be fenced or unfenced, because the primary is the node that does the fencing and unfencing.
User Response: Do not specify the primary node.
| 0028-150 | IP address IP_address for Node host_name not found in SDR. |
Explanation: Unable to find the IP address, which is derived from the host name using the host command, in the Adapter class.
User Response: Specify a correct hostname or fix the IP address.
| 0028-151 | Unable to retrieve oncoming_primary_backup_name from Switch_partition object in SDR. |
Explanation: Attempted to read the oncoming_primary_backup_name from the Switch_partition class in the System Data Repository, but the attempt was not successful.
User Response: Check to see if the System Data Repository is operating correctly.
| 0028-152 | Unable to retrieve the oncoming primary backup node_number from Node object in SDR. |
Explanation: Attempted to read the oncoming_primary_backup_name from the Switch_partition class in the System Data Repository, but the attempt did not succeed.
User Response: Check to see if the System Data Repository is operating correctly.
| 0028-155 | Unable to retrieve System Partition data from the SDR. |
Explanation: The attempt to read the Syspar_map class in the System Data Repository to retrieve the System Partition address was not successful.
User Response: This is either an incorrect node number or the System Data Repository is in an inconsistent or unusable state. Specify a correct node number or investigate the problem.
| 0028-156 | Unable to retrieve the reliable hostname for node number node_number from the SDR. |
Explanation: The attempt to retrieve the reliable hostname for the indicated node number was not successful.
User Response: Specify a correct node number or investigate the problem with the System Data Repository.
| 0028-157 | Remote execution of the request to Primary_name failed. |
Explanation: A remote command to the primary node was not successful.
User Response: Check the authentication and connectivity to the primary node.
| 0028-158 | No nodes to unfence. |
Explanation: After validating arguments, could not find nodes to unfence.
User Response: Specify valid nodes.
| 0028-159 | Unable to find the System Partition containing the node specified by Entered_node_specification. |
Explanation: The specified node was not found in the Syspar_map class.
User Response: Specify a valid node.
| 0028-160 | Unable to find the reliable hostname for the node specified by Entered_node_specification. |
Explanation: Unable to retrieve the reliable_hostname for the node specified.
User Response: Specify a valid node.
| 0028-161 | Unable to find the switch responds entry for the node specified by Entered_node_specification. |
Explanation: Unable to find the switch responds entry for the node specified.
User Response: Specify a valid node.
| 0028-162 | Node specified by entered_node_specification is not currently fenced. |
Explanation: The specified node is not fenced.
User Response: Specify a fenced node.
| 0028-163 | Node specified by entered_node_specification is not on the switch. |
Explanation: The specified node is not on the switch.
User Response: Specify a node that is on the switch.
| 0028-166 | Node number node_number designates the Primary backup node. The Primary backup node cannot be fenced or unfenced. |
Explanation: The indicated node number belongs to the primary backup node, which cannot be fenced or unfenced.
User Response: Do not specify the primary backup node.
| 0028-167 | The autojoin flag is not supported when autounfence is enabled. |
Explanation: The Efence command does not support the autojoin flag on systems where the automatic unfence feature is enabled.
User Response: Reissue the Efence command without specifying the autojoin flag.
| 0028-170 | Unable to retrieve the partition name from the Syspar object in the SDR. |
Explanation: The attempt to read the syspar_name from the Syspar class in the System Data Repository was not successful.
User Response: Check to see that the System Data Repository daemon is running and that the Syspar class has not been corrupted.
| 0028-171 | Cannot ping bootserver bootserver_node_name trying cws. |
Explanation: The attempt to ping the bootserver before using it to distribute the topology file was not successful.
User Response: Use the control workstation.
| 0028-172 | Distribution of topology to bootservers failed rc=pcp_return_code. See the log file on the primary node for details. |
Explanation: The attempt to distribute the topology file to the bootserver through pcp was not successful.
User Response: Check the return code and the status of the bootserver node. Check the log file for any error messages generated from the pcp command.
| 0028-173 | Bad return code from distribution of topologies, not all nodes may have the topology file rc=pexscr_return_code. |
Explanation: The attempt to distribute the topology file to the secondary through pexscr was not successful for some or all of the nodes.
User Response: Check the return code and the status of the secondary nodes. Estart continues with nodes that did not experience this error.
| 0028-174 | Unable to distribute topology file to the following nodes. They will not be unfenced: list_of_nodes. |
Explanation: The attempt to distribute the topology file to the nodes was not successful. These nodes may not have the proper file and should not be unfenced.
User Response: Check to see if the nodes are available on the Ethernet and make sure they have enough space or proper permissions for the topology file.
| 0028-175 | Cannot determine topology file to distribute from topology.data. /var/adm/SPlogs/css/topology.data file not found. |
Explanation: The attempt to distribute the topology file to the nodes was not successful because the topology.data file could not be found in the /var/adm/SPlogs/css directory. This file is created by the Estart command.
User Response: Check whether the /var file system on the primary node is full. If not, try issuing the Estart command, then retry the original command.
| 0028-176 | Unable to distribute topology file to any nodes. Check host_responds for the nodes. |
Explanation: The attempt to distribute the topology file to the nodes was not successful because the nodes either had host_responds down or none of the nodes has a css adapter.
User Response: Check whether host_responds is working on the system.
| 0028-177 | Received errors in distribution of topology file to /tmp on at least one bootserver. See /var/adm/SPlogs/css/dist_topology.log on primary node for details. |
Explanation: The attempt to distribute the topology file to the bootservers was not successful. The file/var/adm/SPlogs/css/dist_topology.log has the system error messages. Probable reasons are Kerberos authentication on the node was not successful or the node has a DASD space problem.
User Response: Check the log and correct the error. Retry the command.
| 0028-178 | Received errors in distribution of topology file from bootserver to at least one node. See /var/adm/SPlogs/css/dist_topology.log on primary node for details. |
Explanation: The attempt to distribute the topology file to the node from a bootserver was not successful. The file /var/adm/SPlogs/css/dist_topology.log has the system error messages.
Probable reasons are Kerberos authentication on the node was not successful or the node has a DASD space problem.
User Response: Check the log and correct the error. Retry the command.
| 0028-179 | Unable to distribute topology file to the following nodes. auto-unfence will continue. |
Explanation: Attempt to distribute the topology file to the node during auto-unfence failed. However, auto-unfence will continue because there is a chance that the topology file is already on the node, due to a previous Estart.
User Response: Check the file /var/adm/SPlogs/css/dist_topology.log for errors.
| 0028-180 | Eunpartition failed -- insufficient memory. |
Explanation: An internal error was detected.
User Response: Record the above information and contact the IBM Support Center.
| 0028-181 | Eunpartition failed -- daemon busy. Retry command. |
Explanation: The fault service daemon is processing a request.
User Response: Retry the command.
| 0028-183 | No css0 adapter found on this node. |
Explanation: A css0 adapter was not found in the ODM on this node.
User Response: Verify that the node has a css0 adapter installed.
| 0028-184 | Note: number of bad switch links switch to switch link(s) did not initialize. Switch performance may be affected. |
Explanation: Some number of switch to switch links did not initialize during Estart command processing. This can affect switch performance. Possible causes are unseated, missing or faulty switch-to-switch cables or other switch hardware problems.
User Response: Review the out.top file for more details.
| 0028-185 | Switch initialization failed on hostname -- Estart already in progress. |
Explanation: Fault service daemon is busy processing an Estart request.
User Response: Wait for Estart to complete.
| 0028-186 | Unable to modify switch_responds object in SDR for node reliable hostname. |
Explanation: SDRChangeAttrValues did not succeed for switch_responds object.
User Response: Check that the System Data Repository is operating correctly.
| 0028-187 | Fault service processes fault service daemon process ids will not die. |
Explanation: Fault service daemon programs did not respond to kill commands.
User Response:
| 0028-188 | Incorrect adapter type. |
Explanation: An unsupported adapter type was found in the ODM on the node.
User Response:
| 0028-189 | Failed to obtain DCE credentials -- rc = return code. Continuing. |
Explanation: The dsrvtgt command returned a non-zero return code.
User Response: Make sure that DCE is configured and is operating correctly.
| 0028-190 | Adapter Configuration failed. |
Explanation: The adapter configuration status found in the ODM indicates a configuration problem.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-191 | No adapter_status attribute in CuAT object class. Attribute assumed to be default value "not_configured". |
Explanation: There was no adapter configuration status found in the ODM.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-192 | rc.switch failed -- date. |
Explanation: The problem of adapter configuration means that the rc.switch is unable to complete successfully.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-193 | Unable to update Adapter Configuration in SDR. SDR returned return code. |
Explanation: The SDRChangeAttrValues command returned a non-zero return code.
User Response: Check that the System Data Repository is operating correctly.
| 0028-194 | ODM adapter_status = adapter_config_status from ODM. |
Explanation: The adapter configuration status in the ODM is css_ready.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-195 | No netmask or netaddr attribute in CuAt object class. |
Explanation: The necessary configuration information could not be found in the ODM.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-196 | Node not customized correctly. |
Explanation: The node has not been customized correctly.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-197 | No switch_node_num, switch_number, switch_chip, or switch_chip_port attribute in CuAt object class. |
Explanation: The necessary configuration information could not be found in the ODM.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-198 | /usr/lpp/ssp/ifconfig failed. |
Explanation: The ifconfig command returned a non-zero return code.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-199 | /usr/lpp/ssp/css/ifconfig down failed. |
Explanation: The ifconfig down command returned a non-zero return code.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-200 | rc.switch entry not in the /etc/inittab file. |
Explanation: The /etc/inittab entry for rc.switch is missing.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-201 | Timed out waiting for switch interface to come up. |
Explanation: The time-out value was exceeded while waiting for the switch interface to be available.
User Response: See the chapter on diagnosing switch problems in the PSSP: Diagnosis Guide.
| 0028-203 | fault service daemon not running on primary node. |
Explanation: The fault service daemon not running on primary node.
User Response: See the chapter on diagnosing switch problems in PSSP: Diagnosis Guide for information on verifying primary nodes.
| 0028-204 | Command not valid on SP Switch system. |
Explanation: This command is used to manage an SP Switch2 system and is only valid on a system with an SP Switch2 installed.
User Response: Use a command which is valid on an SP Switch system.
| 0028-205 | Unable to update CSS Adapter type in SDR. SDR returned return code. |
Explanation: The SDRChangeAttrValues command returned a non-zero return code.
User Response: Check that the System Data Repository is operating correctly.
| 0028-206 | Warning: Cannot ping the oncoming primary node: oncoming primary node. |
Explanation: The node which is to be the oncoming primary node could not be pinged.
User Response: Either ensure that the oncoming primary node is working correctly or select a new oncoming backup node using the Eprimary command.
| 0028-207 | Cannot ping the oncoming primary backup node: oncoming primary backup node. |
Explanation: The node which is to be the oncoming primary backup node could not be pinged.
User Response: Either ensure that the oncoming primary backup node is operating correctly or select a new oncoming primary backup node using the Eprimary command.
| 0028-250 | Command not valid on SP Switch2 system. |
Explanation: This command is used to manage an SP switch and is only valid on a system with an SP switch installed.
User Response: Use a command which is valid on an SP Switch2 system.
| 0028-251 | Unable to modify Switch_plane object in SDR. |
Explanation: SDRChangeAttrValues was not successful for Switch_plane object.
User Response: Check that the System Data Repository is working correctly.
| 0028-252 | Unable to query Switch_plane object in SDR. |
Explanation: SDRGetObjects was not successful for Switch_plane object.
User Response: Check that the System Data Repository is working correctly.
| 0028-253 | The --p flag is not valid on an SP Switch system. |
Explanation: The --p flag can only be used on an SP Switch2 system.
User Response: Enter the command again using the correct syntax.
| 0028-254 | A primary or backup value in the Switch_plane is null or invalid. |
Explanation: One of the primary or backup values for the switch primary node is not valid or may be null.
User Response: Set the value using the Eprimary command.
| 0028-255 | Unable to create Switch_plane object. |
Explanation: SDRCreateObjects did not succeed for Switch_plane object.
User Response: Check that the System Data Repository is operating correctly.
| 0028-256 | The --m flag is not valid on an SP Switch2 system. |
Explanation: The --m flag can only be used on an SP Switch2 system.
User Response: Enter the command again using the correct syntax.
| 0028-257 | Unable to retrieve oncoming_primary_backup_name from Switch_plane object in SDR. |
Explanation: The attempt to read the oncoming_primary_backup_name from the Switch_plane Class in the System Data Repository was not successful.
User Response: Ensure that the System Data Repository is operating correctly.
| 0028-258 | Cannot ping node node name. |
Explanation: An attempt to ping the node node name was not successful.
User Response: Ensure that the node is up and operating correctly.
| 0028-259 | Cannot issue a remote command to node node name. |
Explanation: An attempt to issue a remote command to the node node name was unsuccessful.
User Response: Ensure that the node is up and operating correctly for your security environment.
| 0028-260 | The backup node primary backup node cannot be pinged, so you may not fence the primary node primary node. |
Explanation: The primary node may be fenced only if the backup node is available.
User Response: To fence the primary node, select a new primary node with the Eprimary command and run Estart. Then, fence the old primary node.
| 0028-261 | A primary or backup value in the Switch_plane is null or invalid. |
Explanation: One of the primary or backup values for the switch primary node is not valid or is set to null.
User Response: Set the value using the Eprimary command.
| 0028-262 | The fault-service daemon is not up on the backup node primary backup node, so you may not fence the primary node primary node. |
Explanation: The primary node may be fenced only if the backup node is available.
User Response: To fence the primary node, select a new primary node with the Eprimary command and run Estart. Then, fence the old primary node.
| 0028-263 | The backup node primary backup node, is isolated, so you may not fence the primary node primary node. |
Explanation: The primary node may be fenced only if the backup node is available.
User Response: To fence the primary node, select a new primary node with the Eprimary command and run Estart. Then, fence the old primary node.
| 0028-264 | There is no backup node, so you may not fence the primary node primary node. |
Explanation: The primary node may be fenced only if the backup node is available.
User Response: To fence the primary node, select a new primary node with the Eprimary command and run Estart. Then, fence the old primary node.
| 0028-265 | There are no other nodes which are not isolated, so you may not fence the primary node primary node and the backup node primary backup node. |
Explanation: In order to fence the primary node and the backup node, you must have at least one other node available.
User Response: Make another node available using Eunfence.
| 0028-266 | Cannot ping the only other node which is not isolated, last good node so you may not fence the primary node primary node and the primary backup node primary backup node. |
Explanation: In order to fence the primary node and the backup node, you must have at least one other node available.
User Response: Make another node available using Eunfence.
| 0028-267 | The fault-service daemon is not running on the only other node which is not isolated last good node so you may not fence the primary node primary node and the primary backup node primary backup node. |
Explanation: In order to fence the primary node and the backup node, you must have at least one other node available.
User Response: Ensure that the fault service daemon is running on some other node.
| 0028-280 | Cannot ping the oncoming primary node: oncoming primary node. |
Explanation: An attempt to ping the primary node was unsuccessful.
User Response: Pick a new primary node using Eprimary, then issue Estart.
| 0028-281 | Cannot ping the oncoming primary backup node: oncoming primary backup node. |
Explanation: An attempt to ping the primary backup node was unsuccessful.
User Response: Pick a new oncoming primary backup node using Eprimary.
| 0028-282 | Fault service worm not up on oncoming primary node: oncoming primary node. |
Explanation: None.
User Response: Pick a new oncoming primary node using Eprimary.
| 0028-283 | Fault service worm not up on oncoming primary backup node: oncoming primary backup node. |
Explanation: None.
User Response: Pick a new oncoming primary backup node using Eprimary.
| 0028-284 | Oncoming primary node is fenced: oncoming primary node. |
Explanation: None.
User Response: Pick a new oncoming primary node using Eprimary.
| 0028-285 | Oncoming primary backup node is fenced: oncoming primary backup node. |
Explanation: None.
User Response: Pick a new oncoming primary backup node using Eprimary.
| 0028-286 | Neither the oncoming primary nor the oncoming primary backup node is available, cannot Estart. |
Explanation: At least one of the oncoming primary and oncoming primary backup nodes is needed to Estart.
User Response: Select a new oncoming primary node and a new oncoming primary backup node using Eprimary.
| 0028-287 | The Eprimary command returned an error, cannot Estart. |
Explanation: Estart attempted to pick a new primary node using Eprimary.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-288 | plane plane number: program name: unable to query Switch_plane object in SDR. |
Explanation: SDRChangeAttrValues was not successful for Switch_plane object.
User Response: Make sure that the System Data Repository is operating correctly.
| 0028-289 | plane plane number: program name: unable to modify Switch_plane object in SDR. |
Explanation: SDRGetObjects was not successful for Switch_plane object.
User Response: Make sure that the System Data Repository is operating correctly.
| 0028-290 | plane plane number: program name: unable to create Switch_plane object. |
Explanation: SDRCreateObjects was not successful for Switch_plane object.
User Response: Make sure that the System Data Repository is operating correctly.
| 0028-291 | plane plane number: program name: A primary or backup value in the Switch_plane is null or invalid. |
Explanation: One of the primary or backup values for the switch primary node is null or not valid (probably null).
User Response: Set the value using the Eprimary command.
| 0028-292 | plane plane number: program name: Primary node not defined -- use Eprimary. |
Explanation: A primary node must be assigned before running Estart.
User Response: See the man page for this command for information on how to assign a primary node.
| 0028-293 | plane plane number: program name: Warning: Cannot ping the oncoming primary node: oncoming primary node. |
Explanation: The node which is to be the oncoming primary node could not be pinged.
User Response: Either ensure that the oncoming primary node is functioning correctly or select a new oncoming backup node using the Eprimary command.
| 0028-294 | plane plane number: program name: Warning: Cannot ping the oncoming primary backup node: oncoming primary backup node. |
Explanation: The node which is to be the oncoming primary backup node could not be pinged.
User Response: Either ensure that the oncoming primary backup node is functioning correctly or select a new oncoming primary backup node using the Eprimary command.
| 0028-295 | plane plane number: program name: Fault service worm not up on oncoming primary node, cannot Estart: node name. |
Explanation: The worm daemon on the oncoming primary node is not up. This message may also appear if Estart is unable to issue a remote command to the oncoming primary node.
User Response: Rerun rc.switch on the oncoming primary node or choose another node using Eprimary. If the problem is due to a remote command failure, check the Kerberos authentication setup.
| 0028-296 | plane plane number: program name: Fault service worm not up on oncoming primary backup node, cannot Estart: node name. |
Explanation: The worm daemon on the oncoming primary backup node is not up. This message may also appear if Estart is unable to issue a remote command to the oncoming primary backup node.
User Response: Rerun rc.switch on the oncoming primary backup node or choose another node using Eprimary. If the problem is due to a remote command failure, check the Kerberos authentication setup.
| 0028-297 | plane plane number: program name: Oncoming primary node is fenced, cannot Estart: node name. |
Explanation: The oncoming primary node to be used by Estart is fenced.
User Response: Check the node and possibly, select an alternate oncoming primary node using the Eprimary command.
| 0028-298 | plane plane number: program name: Note: oncoming primary backup node is fenced: node name. |
Explanation: The node is fenced off.
User Response: There is no problem as long as the node is unfenced before issuing Estart.
| 0028-299 | plane plane number: program name: Neither the oncoming primary nor oncoming primary backup node is available, cannot Estart. |
Explanation: At least one of the oncoming primary and oncoming primary backup nodes is needed to Estart.
User Response: Select a new oncoming primary node and a new oncoming primary backup node using Eprimary.
| 0028-300 | plane plane number: program name: The Eprimary command returned an error, cannot Estart. |
Explanation: Estart attempted to pick a new primary node using Eprimary.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-301 | plane plane number: program name: The autojoin flag is not supported when autounfence is enabled. |
Explanation: The Efence command does not support the autojoin flag when the automatic unfence feature is enabled.
User Response: Reissue the Efence command without specifying the autojoin flag.
| 0028-305 | Adapter configuration failed for adapter adapter name. |
Explanation: The adapter configuration status found in the ODM indicates a configuration error.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-306 | Unable to update Adapter Configuration for adapter name in SDR. SDR returned error code. |
Explanation: The SDRChangeAttrValues command returned a non-zero return code.
User Response: Check that the System Data Repository is operating correctly.
| 0028-307 | Unable to update CSS Adapter type for adapter name in SDR. SDR returned return code. |
Explanation: The SDRChangeAttrValues command returned a non-zero return code.
User Response: Check that the SDR is operating correctly.
| 0028-308 | No netmask or netaddr attribute in CuAt object class for adapter name. |
Explanation: The necessary configuration information could not be found in the ODM.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-309 | /usr/lpp/ssp/css/ifconfig failed for adapter name. |
Explanation: The ifconfig command returned a non-zero return code.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-310 | /usr/lpp/ssp/css/ifconfig down failed for adapter name. |
Explanation: The ifconfig down command returned a non-zero return code.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0028-320 | plane plane number: program name Unable to retrieve the topology file out of SDR. |
Explanation: Unable to retrieve the topology file out of the System Data Repository.
User Response: Check that the System Data Repository is operating correctly.
| 0028-321 | plane plane number: program name Unable to retrieve oncoming_primary_backup_name from Switch_plane object in SDR. |
Explanation: Attempted to read the oncoming_primary_backup_name from the Switch_partition Class in the System Data Repository. The attempt was not successful.
User Response: Check that System Data Repository is operating correctly.
| 0028-322 | plane plane number: program name Unable to retrieve the oncoming primary backup node_number from Node object in SDR. |
Explanation: Attempted to read the oncoming primary backup node_number from the Node Class in the System Data Repository. The attempt was not successful.
User Response: Check that System Data Repository is operating correctly.
| 0028-323 | plane plane number: program name Switch initialization failed on hostname - i_stub call error. |
Explanation: Internal error.
User Response: Contact the IBM Support Center.
| 0028-324 | plane plane number: program name Switch initialization failed on hostname - insufficient memory. |
Explanation: Internal error.
User Response: Contact the IBM Support Center.
| 0028-325 | plane plane number: program name Switch initialization failed on hostname - Estart already in progress. |
Explanation: Fault service daemon is busy processing an Estart request.
User Response: Wait for the Estart request to complete.
| 0028-326 | plane plane number: program name Switch initialization failed on hostname - daemon busy. Retry command. |
Explanation: Fault service daemon is busy processing a request.
User Response: Retry the command.
| 0028-327 | plane plane number: program name Switch initialization failed on hostname - i_stub problem. |
Explanation: Internal error.
User Response: Contact the IBM Support Center.
| 0028-328 | plane plane number: program name Switch initialization failed. The fault_service_Worm_RTG_CS daemon exited on hostname due to errors. See the flt file on the switch primary in the appropriate sub-directory of /var/adm/SPlogs for more information. |
Explanation: Switch initialization was not successful. failed. The fault_service_Worm_RTG_SP daemon has encountered errors and has exited.
User Response: Review /var/adm/SPlogs/css/flt file. Then, consult the PSSP: Diagnosis Guide.
| 0028-329 | plane plane number: program name Switch initialization hostname second time limit exceeded. The fault_service_Worm_RTG_CS daemon is continuing to attempt to initialize the switch. See the flt file on the switch primary in the appropriate sub-directory of /var/adm/SPlogs for more information. |
Explanation: Estart processing has exceeded allowable time limit.
User Response: Consult the PSSP: Diagnosis Guide.
| 0028-330 | plane plane number: program name Unable to find suitable primary backup node. No primary backup node running. |
Explanation: The oncoming primary backup node in the System Data Repository was not available. Either the Ethernet is down, the daemon is not running, or the primary backup node is fenced. The switch attempted to choose another node, but was not able to find an available node. The switch is running on the primary node.
User Response: Estart continues. Make sure you intend to run only on the one node. If the reason a primary backup node could not be assigned is because the nodes are fenced, run the Eunfence command to unfence one or more nodes, and run the Estart command again.
| 0028-331 | plane plane number: program name Note: number of bad links switch to switch links did not initialize. Switch performance may be affected. |
Explanation: Some number of switch to switch links did not initialize during Estart. This can affect switch performance. Possible causes are un-setted, missing or faulty switch-to-switch cable or other switch hardware problem.
User Response: Review the out.top file for more details.
| 0028-332 | plane plane number: program name Unable to store topology file in SDR. |
Explanation: SDRCreateFile was not successful storing the topology file.
User Response: Check that the System Data Repository is operating correctly.
| 0028-333 | plane plane number: program name Error return from Etopology |
Explanation: Unsuccessful running Etopology.
User Response: Check to see that you specified the correct file name.
| 0028-334 | plane plane number: program name Primary node not defined - use "Eprimary".. |
Explanation: A primary node must be assigned before running the Estart command.
User Response: See the Eprimary command man page for information on how to assign a primary node.
| 0028-335 | plane plane number: program name Can not ping the primary node: primary node. |
Explanation: The primary node cannot be pinged.
User Response: See the PSSP: Diagnosis Guide for more information.
| 0028-336 | plane plane number: program name No functional switch primary node, run Estart. |
Explanation: There is no node running as the primary. This is the initial state of the system or will happen when rc.switch is run on the current primary node. It can also happen in a brief window when primary node takeover is occurring.
User Response: Check Eprimary for more information and run the Estart command, if necessary.
| 0028-337 | plane plane number: program name Node number node number designates the Primary Node. The Primary node cannot be fenced without the -f flag. |
Explanation: Node number given belongs to the Primary node, which cannot be fenced without using the -f flag.
User Response: Do not specify the Primary node unless you also specify the -f flag.
| 0028-338 | plane plane number: program name Unable to find the switch responds entry for the node specified by node number. |
Explanation: Unable to find the switch responds entry for the node specified.
User Response: Specify a valid node again.
| 0028-339 | plane plane number: program name Node specified by node number is not on the switch. |
Explanation: Specified node is not on the switch.
User Response: Specify a node that is on the switch.
| 0028-340 | plane plane number: program name Node number node number designates the Primary Backup Node. The Primary Backup node cannot be fenced without the -f flag. |
Explanation: Node number given belongs to the Primary Backup node, which cannot be fenced without the -f flag.
User Response: Do not specify the Primary backup node without specifying the -f flag.
| 0028-341 | plane plane number: program name The backup node primary backup node cannot be pinged, so you may not fence the primary node primary node. |
Explanation: The primary node may be fenced only if the backup node is available.
User Response: To fence the primary node, select a new primary node with the Eprimary command and issue Estart. Then, fence the old primary node.
| 0028-342 | plane plane number: program name A primary or backup value in the Switch_plane is null or invalid. |
Explanation: One of the primary or backup values for the switch primary node is invalid (probably null).
User Response: Set the value using the Eprimary command.
| 0028-343 | plane plane number: program name The fault-service daemon is not up on the backup node primary backup node, so you may not fence the primary node primary node. |
Explanation: The primary node may be fenced only if the backup node is available.
User Response: To fence the primary node, select a new primary node with the Eprimary command and issue Estart. Then, fence the old primary node.
| 0028-344 | plane plane number: program name The backup node primary backup node is isolated, so you may not fence the primary node primary node. |
Explanation: The primary node may be fenced only if the backup node is available.
User Response: To fence the primary node, select a new primary node with the Eprimary command and issue Estart. Then, fence the old primary node.
| 0028-345 | plane plane number: program name There is no backup node, so you may not fence the primary node primary node. |
Explanation: The primary node may be fenced only if the backup node is available.
User Response: To fence the primary node, select a new primary node with the Eprimary command and issue Estart. Then, fence the old primary node.
| 0028-346 | plane plane number: program name There are no other nodes which are not isolated, so you may not fence the primary node primary node and the backup node primary backup node. |
Explanation: In order to fence the primary node and the backup node, you must have at least one other node available.
User Response: Make another node available using Eunfence.
| 0028-347 | plane plane number: program name Cannot ping the only other node which is not isolated, last valid node, so you may not fence the primary node primary node and the backup node primary backup node. |
Explanation: In order to fence the primary node and the backup node, you must have at least one other node available.
User Response: Make another node available using Eunfence.
| 0028-348 | plane plane number: program name The fault-service daemon is not running on the only other node which is not isolated, last good node, so you may not fence the primary node primary node, and the backup node primary backup node. |
Explanation: In order to fence the primary node and the backup node, you must have at least one other node available.
User Response: Ensure that the fault service daemon is running on some other node.
| 0028-349 | plane plane number: program name No nodes to unfence. |
Explanation: After validating arguments, no nodes were found to unfence.
User Response: Specify valid nodes.
| 0028-350 | plane plane number: program name Node specified by node specified is not currently fenced. |
Explanation: Specified node is not fenced.
User Response: Specify a fenced node.
| 0028-351 | plane plane number: program name Oncoming primary node is fenced primary node name. |
Explanation: None.
User Response: Pick a new oncoming primary node using Eprimary.
| 0028-352 Command not supported on nodes in restricted root rcmd mode. |
Explanation: This command is not supported from an SP system node when your system is running in restricted root remote command mode.
User Response: Reissue the command from the control workstation.
| 0028-354 | startsrc failed for daemon mld. |
Explanation: The startsrc command returned a non-zero return code.
User Response: Analyze the return code to determine the cause of the failure.
| 0028-355 | /usr/lpp/ssp/css/ifconfig failed for ml0. |
Explanation: The ifconfig command returned a non-zero return code.
User Response: Analyze the return code to determine the cause of the failure.
| 0028-356 | Definition failed for device driver ml. |
Explanation: The mkdev command returned a non-zero return code.
User Response: Analyze the return code to determine the cause of the failure.
| 0028-357 | plane plane number: program name Warning: Cannot ping the oncoming primary node: primary node name. |
Explanation: An attempt to ping the primary node was unsuccessful.
User Response: Pick a new primary node using Eprimary, then issue Estart.
| 0028-358 | plane plane number: program name Fault service worm not up on oncoming primary node: primary node name. |
Explanation: None.
User Response: Pick a new oncoming primary node using Eprimary.
| 0028-359 | plane plane number: program name Warning: Cannot ping the oncoming primary backup node: primary node name. |
Explanation: An attempt to ping the primary backup node was unsuccessful.
User Response: Pick a new oncoming primary backup node using Eprimary.
| 0028-360 | plane plane number: program name Warning: Fault service worm not up on oncoming primary backup node: primary node name. |
Explanation: None.
User Response: Pick a new oncoming primary backup node using Eprimary.
| 0028-361 | Node number node name designates the Primary Node. The Primary node cannot be unfenced. |
Explanation: None.
User Response: Pick a new oncoming primary backup node using Eprimary.
| 0028-362 | Node number node name designates the Primary Backup Node. The Primary Backup node cannot be unfenced. |
Explanation: None.
User Response: Pick a new oncoming primary backup node using Eprimary.
| 0028-363 | plane plane number: program name Node number node name designates the Primary Node. The Primary node cannot be unfenced. |
Explanation: None.
User Response: Pick a new oncoming primary backup node using Eprimary.
| 0028-364 | plane plane number: program name Node number node name designates the Primary Backup Node. The Primary Backup node cannot be unfenced. |
Explanation: None.
User Response: Pick a new oncoming primary backup node using Eprimary.
| 0028-365 | Selected Node(s): node_list not part of the Switch fabric. |
Explanation: The nodes selected cannot be used because they are not configured for the switch fabric. Neither the Primary node nor the Backup node values are changed in the SDR.
User Response: Reissue the Eprimary command using nodes that are part of the Switch fabric.
| 0028-501 | add_attr() error. rc=return code. |
Explanation: The attribute does not exist or it is an incorrect attribute name.
User Response: Use lsattr -D -l device_ name to verify predefined attributes.
| 0028-502 | error during odm_initialize. |
Explanation: The call to odm_initialize() to start the Object Data Manager(ODM) was not successful. The odmerrno variable has been set to indicate the error.
User Response: Use the odmerrno value to determine the reason for error.
| 0028-503 | error during odm_lock |
Explanation: The call to odm_lock() to start to look at ODM data, was unsuccessful.
User Response: Another program may have locked ODM data. Try again later.
| 0028-504 | error during odm_open_class(CuDv_CLASS)" |
Explanation: ODM Customized Devices (CuDv) object class was not successful in opening.
User Response: Use odmget CuDv to query the ODM. Retry the operation and report to the IBM Support Center if the problem persists.
| 0028-505 | No CuDv with this logical device logical device name. |
Explanation: There is no customized device data for the given logical device.
User Response: Use odmget -q name=the_logical_device CuDv to query ODM. Also, check that you have supplied the correct device name.
| 0028-506 | error during odm_get_first. |
Explanation: The call, odm_get_first() to get CuDv data, was not successful.
User Response: Use odmget -q name=the_logical_device CuDv to query the ODM. Also, check that you have supplied the correct device name. Retry the operation and report to the IBM Support Center if the problem persists.
| 0028-507 | Error reading CuAt with return code. |
Explanation: The call, odm_get_list() to open Customized Device Attribute (CuAt, was not successful. The attribute does not exist or the attribute name was not valid.
User Response: Use lsattr -D -l device_name to verify predefined attributes
| 0028-508 | No PdDv for this device |
Explanation: The attribute does not exist or the attribute name is not valid.
User Response: Use lsattr -D -l device_name to verify predefined attributes
| 0028-509 | Failed in updating device driver. |
Explanation: This program was not successful in updating the attribute in device driver.
User Response: Check to see if the device driver is configured. If it is configured, retry the operation and contact the IBM Support Center if the problem persists.
| 0028-510 | Failed in updating ODM attributes |
Explanation: This program was not successful in updating the ODM.
User Response: Retry the operation and contact the IBM Support Center if the problem persists.
| 0028-511 | odm_close_class() error |
Explanation: This program was not successful in closing ODM classes.
User Response: Retry the operation and contact the IBM Support Center if the problem persists.
| 0028-512 | Error Opening CuAt |
Explanation: Opening Customized Attribute class was not successful.
User Response: Use lsattr -D -l device_name to verify predefined attributes.
| 0028-513 | Error Opening PdAt where return code. |
Explanation: Opening Predefined Attribute data in ODM was not successful.
User Response: Use lsattr -D -l device_name to verify predefined attributes.
| 0028-514 | No records in PdAt where search string containing device type and attribute. |
Explanation: The attribute does not exist or the attribute name is not valid.
User Response: Use lsattr -D -l device_name to verify predefined attributes.
| 0028-515 | Error reading CuAt where search string containing logical name and attribute name. |
Explanation: The attribute does not exist or the attribute name is not valid.
User Response: Use lsattr -D -l device_name to verify predefined attributes.
| 0028-516 | Failure closing CuAt object class |
Explanation: This program was not successful closing the ODM CuAt object class.
User Response: Retry the operation and contact the IBM Support Center if the problem persists.
| 0028-517 | Failure closing PdAt object class |
Explanation: This program was not successful closing the ODM PdAt object class.
User Response: Retry the operation and contact the IBM Support Center if the problem persists.
| 0028-518 | Invalid value for attribute attribute name is attribute value. |
Explanation: The attribute value mismatch the attribute type.
User Response: Use lsattr -D -l device_name to verify predefined attributes and their values.
| 0028-519 | The value must be represented by a total number of bytes. |
Explanation: This program expects a numeric parameter for the given attribute.
User Response: Retry using a numeric parameter.
| 0028-520 | The pool size must be a multiple of 2 MB. |
Explanation: The IP send pool and receive pool size must be a multiple of 2 Mega bytes.
User Response: Retry and enter a pool size of a multiple of 2 MB.
| 0028-521 | null attribute or value |
Explanation: The attribute value is missing.
User Response: Check the command usage.
| 0028-522 | IP is not configured. However, the pool size has been registered in the device driver. |
Explanation: The SP Switch IP protocol has not been configured. The given pool size is not updated in the IP protocol.
User Response: None.
| 0028-523 | win_minsize cannot be greater than win_maxsize. |
Explanation: The win_minsize value cannot be greater than the win_maxsize value.
User Response: Either enlarge the win_maxsize value or decrease the win_minsize value.
| 0028-527 | The given attribute name (spool or rpool size), value should not be greater than 32 MB. |
Explanation: Neither send pool size or receive pool size can be greater than 32 mega bytes.
User Response: Enter the command again with a pool size not greater than 32 MB.
| 0028-528 | Failed to get current attribute name attribute from ODM. |
Explanation: The attribute does not exist or the attribute name is not valid.
User Response: Use lsattr -E -l device_name to verify predefined attributes.
| 0028-529 | The provided component ID component ID has reserved windows. |
Explanation: The component ID has had reserved windows in the driver.
User Response: Use lsattr -E -l device_name to verify if it has reserved window or not. If the caller wants to reserve more windows, it should first RELEASE windows then RESERVE windows again.
| 0028-530 | The provided component ID component ID has not reserved windows. |
Explanation: The component ID has not reserved windows in the driver. The component was not successful in RELEASE windows.
User Response: Use lsattr -E -l device_name to verify if it has a reserved window.
| 0028-531 | Some windows of the provided component ID component ID have not been unloaded. |
Explanation: In order to release reserved window, the window must be unloaded.
User Response: Make sure that the application which uses the window has been terminated.
| 0028-532 | Only one attribute is allowed in one chgcss command if window attribute is specified. |
Explanation: The chgcss command can change one window attribute per time.
User Response: Issue more than one chgcss commands to change window attributes.
| 0028-533 | Either component ID, or type, or count is missing in RESERVE window request. |
Explanation: In order to reserve windows, the caller must provide the component ID, type, and count.
User Response: Check the syntax and call chgcss again
| 0028-534 | Component ID is missing in RELEASE window request. |
Explanation: In order to release windows, the caller must provide the component ID.
User Response: Check the syntax and call chgcss again
| 0028-535 | Wrong cmd value wrong command value in window request. |
Explanation: The correct cmd value is RESERVE, RELEASE, or QUERY.
User Response: Check the syntax and call chgcss again
| 0028-536 | Wrong type value in RESERVE window request. |
Explanation: The correct cmd value is user_client or kernel_client.
User Response: Check the syntax and call chgcss again
| 0028-537 | The component ID component ID is too long. It should not have more than 8 characters. |
User Response: Check the syntax and call chgcss again
| 0028-538 | Wrong count value count value in RESERVE window request. It cannot be greater than largest window number which is the maximum logical window. |
Explanation: Issue lsattr --E --l logical_device_name to determine how many logical windows are on the device.
User Response: Run lsattr -E -l logical device name to determine how many logical windows there are on the device.
| 0028-539 | Count and window list mismatch in changing window attribute. |
Explanation: It might be a program error in RR_WINDOW ioctl call. The returned window number (count) and a list of window numbers do not match.
User Response: Contact the IBM Support Center.
| 0028-f00 | Could not open socket to the SP Switch Admin Daemon (cssadm). |
Explanation: Could not open a socket to the SP Switch Admin Daemon (cssadm).
User Response:
| 0028-f01 | Could not connect to the SP Switch Admin Daemon (cssadm), rc=return code. |
Explanation: Could not connect to the SP Switch Admin Daemon (cssadm).
User Response:
| 0028-f02 | Could not write to the SP Switch Admin Daemon (cssadm), rc=return code. |
Explanation: Could not write to the SP Switch Admin Daemon (cssadm).
User Response:
| 0028-f03 | Failure reading socket from internal Eclock script. |
Explanation: Could not read from the socket to the SP Switch Admin Daemon (cssadm).
User Response:
| 0028-ff0 | Could not execute internal Eclock script filename. |
Explanation: Could not execute the internal Eclock script.
User Response: Check the file permissions on the specified file to make sure that root has execute permission, and rerun the Eclock command.