Some switch fault service deamon error messages are classified according to
their severity as informational (i), note (n), and error (e). These
designations may appear when you receive a message, and should be
noted.
| 2510-195 | The fault service daemon got a SIGTERM signal. |
Explanation: The fault service daemon was terminated by a SIGTERM signal. This is usually caused by someone issuing rc.switch on the node.
User Response: No user action is required. See the chapter on Diagnosing Switch Problems in PSSP: Diagnosis Guide.
| 2510-196 | The fault service daemon got a SIGDANGER signal, probably because the system is low on pg space. |
Explanation: The fault service daemon received a SIGDANGER signal. The usual cause of this condition is low paging space on the node.
User Response: Record the above information and contact the IBM Support Center.
| 2510-197 | The fault service daemon got a SIGBUS signal. |
Explanation: The fault service daemon received a SIGBUS signal, from an exception that occurred, while attempting to access the switch adapter. This is a likely hardware problem.
User Response: See the section on Diagnosing Switch Problems in PSSP: Diagnosis Guide for more information on the Isolating Adapter and Switch Errors. An error log entire should accompany this entry with more details and information that have actions in the section on Isolating Adapter and Switch Errors.
| 2510-291 | Error in get_enable_autounfence(), rc=rc. |
Explanation: The SDR autounfence attribute could not be obtained.
User Response: Check that the SDR is operational and that the automatic unfence attribute (autounfence) is defined. Switch initialization continues with automatic unfence enabled.
| 2510-294 | Unexpected value for autounfence: value. Automatic unfence will be enabled. |
Explanation: The SDR autounfence attribute contained an invalid value.
User Response: The fault service daemon continues with automatic unfence enabled. Run the Estart command with the -autounfence flag to change the attribute value.
| 2510-295 | automatic unfence is [enabled | disabled] (value). |
Explanation: Automatic unfence is enabled or disabled as indicated.
User Response: None.
| 2510-299 | [Efence | Eunfence] msg received, but we are are not the PRIMARY. |
Explanation: A backup or secondary node received a request intended for the primary node. The most likely cause is that the SDR does not accurately reflect the primary node's hostname.
User Response: The backup or secondary node ignores the request. Run the Eprimary command to see the SDR's current settings for the primary and backup nodes. Run the Estart command to update the primary and backup names in the SDR.
| 2510-482 | Backup didn't respond to scan. |
Explanation: The primary backup Fault Service daemon did not respond to a Scan request from the primary. The backup node or Fault Service daemon may not be operational.
User Response: The administrator may want to pick a new backup node and then perform diagnosis on the failing backup node. See the chapter on Diagnosing Switch Problems in PSSP: Diagnosis Guide for more details.
| 2510-606 | A switch Error/Status service packet was received during a broadcast operation. |
Explanation: A switch Error/Status service packet was received by the primary node during a service packet broadcast operation. The fault service daemon takes recovery actions when this occurs.
User Response: Review other messages in the flt file, that were generated near the time-stamp of this entry, to try and isolate the root cause of the problem. If the problem persists, contact IBM Software Support.
| 2510-607 | Timed-out waiting for acknowledgments from broadcast operation. |
Explanation: The fault service daemon on the primary node timed out waiting for an acknowledgment(s) from a node or nodes, during a service packet broadcast operation. The fault service daemon takes recovery actions when this occurs.
User Response: Review other messages in the flt file, that were generated near the time-stamp of this entry to try and isolate the root cause of the problem. If the problem persists, contact IBM Software Support.
| 2510-651 | Service library error. |
Explanation: The fault service daemon's communication library returned an error.
User Response: This is not a normal condition, record the above information and contact the IBM Support Center.
| 2510-712 | generate_service_routes() failed with rc=rc. |
Explanation: The primary node failed to successfully generate service routes for the switch network. The return code from the service route generation function is also displayed. The fault service daemon on this node is terminated. On SP switch systems, the primary backup node will attempt to takeover control of the switch network.
User Response: This is not a normal condition. Record the above information and contact the IBM Support Center.
| 2510-714 | generate_processor_routes() failed with rc=rc. |
Explanation: The primary node failed to successfully generate processor (node to node) routes for the switch network. The return code from the processor route generation function is also displayed. The fault service daemon on this node is terminated.
On SP switch systems, the primary backup node will attempt to takeover control of the switch network.
User Response: This is not a normal condition. Record the above information and contact the IBM Support Center.
| 2510-715 | SetSystemTOD() failed with rc=rc |
Explanation: The primary node failed to successfully synchronize all of the Time-Of-Day counters in the switch network. The switch Time-Of-Day counters are not valid. The fault service daemon on this node is terminated.
On SP switch systems, the primary backup node will takeover control of the switch network.
User Response: This is not a normal condition. Record the above information and contact the IBM Support Center.
| 2510-716 | downLoad_processor_route_table() failed with rc=rc. |
Explanation: The fault service daemon on this node failed to download its processor to processor route table to the kernel and/or switch adapter on the primary node. The fault_service daemon is terminated. On SP switch systems, the primary backup node will take over control of the switch network.
User Response: This is not a normal condition. Record the above information and contact the IBM Support Center.
| 2510-720 | TBIC should not be on device FIFO. |
Explanation: During switch initialization the fault service daemon encountered a TBIC (node) devices on its device FIFO, when it was expecting to process a switch device. The fault_service daemon is terminated. The primary backup node will take over control of the switch network.
User Response: This is not a normal condition. Record the above information and contact the IBM Support Center.
| 2510-727 | Node node name NOT Fenced, rc=rc. |
Explanation: The specified node did not fence successfully.
User Response: See the Diagnosing Switch Problems section of PSSP: Diagnosis Guide for more information on this failure.
| 2510-730 | Node node name NOT UnFenced, rc=rc. |
Explanation: The specified node did not unfence successfully.
User Response: See the Diagnosing Switch Problems section of PSSP: Diagnosis Guide for more information on this failure.
| 2510-731 | Device device ID did not respond. Disabling device. |
Explanation: The device specified in the message, failed to respond to a service packet request from the primary node. The fault service daemon's recovery action in this instance is to remove the device from the switch network configuration.
User Response: This is not a normal condition and the IBM Support Center should be contacted. More details can be found in the out.top file. For more information on this failure, see the section on Device and Link Problems in the Diagnosing Switch Problems chapter of PSSP: Diagnosis Guide.
| 2510-732 | Enodes does not exist, so we assume SDR is in use. |
Explanation: The fault service daemon will use the SDR data and interface.
User Response: None. The message is informational.
| 2510-733 | SDROpenSession failed with a return code return code. |
Explanation: The SDROpenSession function failed with specified return code.
User Response: For more information, see the Diagnosing SDR Problems section in PSSP: Diagnosis Guide.
| 2510-734 | SDRSetClass failed with a return code return code. |
Explanation: The SDRSetClass function failed with specified return code.
User Response: For more information, see the Diagnosing SDR Problems section of PSSP: Diagnosis Guide.
| 2510-735 | SDRAddIntAttrValue failed with a return code return code. |
Explanation: The SDRAddIntAttrValue function failed with the specified return code return code.
User Response: For more information, see the Diagnosing SDR Problems section of PSSP: Diagnosis Guide.
| 2510-736 | SDRAddStringAttrValue failed with a return code return code |
Explanation: The SDRAddStringAttrValue function failed with the specified return code return code
User Response: For more information, see the Diagnosing SDR Problems section of PSSP: Diagnosis Guide.
| 2510-737 | SDRChangeAttrValues failed with a return code return code. |
Explanation: The SDRChangeAttrValues function failed with the specified return code return code.
User Response: For more information, see the Diagnosing SDR Problems section of PSSP: Diagnosis Guide.
| 2510-738 | SDRGetObjects failed with a return code return code. |
Explanation: The SDRGetObjects function failed with specified return code.
User Response: For more information, see the Diagnosing SDR Problems section of PSSP: Diagnosis Guide.
| 2510-739 | SDRFindAttrInObject failed with a return code return code. |
Explanation: The SDRFindAttrInObject function failed with specified return code.
User Response: For more information, see the Diagnosing SDR Problems section of PSSP: Diagnosis Guide.
| 2510-740 | Packet Sequence Number = packet sequence number Switch Time-Of-Day=time of day value. |
Explanation: The packet sequence number and switch Time-Of-Day contained in a switch packet.
User Response: None. The message is informational.
| 2510-741 | Second Error Capture Registers = XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX. |
Explanation: The Second Error Capture Registers contain detailed information on errors detected by a switch chip. There is a byte for each type of error that contains either the number of the port that the error was detected on, or additional information on the type of error.
User Response: None. The message is informational.
| 2510-742 | Transmitting a Reset Error packet; Route = route, Recv Error Resets = receiver error resets, Sender Error Resets = sender error resets, Central Queue Resets = central queue resets, Service Logic Resets = service logic resets. |
Explanation: Switch recovery transmitted a Reset Error packet to a switch chip with specified fields. A Reset Error packet resets a switch chip's first and second error capture registers.
User Response: None. The message is informational.
| 2510-743 | Disabling port port number of chip chip on the switch in slot slot number of frame frame number |
Explanation: Switch recovery code disabling a port on the switch as a recovery action.
User Response: None. This message is informational about a recovery action that was taken. If the port that was disabled is not a Device that was intentionally powered off then contact IBM Hardware service.
| 2510-746 | Error/Status packet received prior to database construction, device id=ID. |
Explanation: An Error/Status packet was received before the switch was initialized. The switch must be initialized before switch recovery will take place.
User Response: This is an abnormal condition Record the above information and contact the IBM Support Center.
| 2510-747 | Transmitting a Read Status packet; Route=route, Device ID=device ID. |
Explanation: Switch recovery transmitted a Read Status packet to a device with the specified device ID. A Read Status packet queries a device for its current error and status information.
User Response: None. The message is informational.
| 2510-748 | The backup node (ID=ID) has been removed from the switch network. |
Explanation: The Primary backup node has been fenced from the switch. A new Primary backup node was chosen.
User Response: None. The message is informational.
| 2510-749 | Turning off switchResponds bits for node node number in the SDR. |
Explanation: Turning off bits in the switch_responds class in the SDR.
User Response: None. This message informs of a switch_responds bit for a Device or Node being turned off.
| 2510-754 | Time out on receive of duplicate packet. |
Explanation: Only one of two responses to a service packet was received.
User Response: None. The message is informational.
| 2510-757 | Unable to locate an entry for device Device ID in the database. |
Explanation: Unable to locate an entry for the specified device in the device database. This should not occur during normal operation.
User Response: Abnormal condition, contact IBM Software Support.
| 2510-758 | Unable to retrieve a service route for device device ID. |
Explanation: No switch route exists to device ID specified. This should not occur during normal operation.
User Response: Abnormal condition, contact IBM Software Support.
| 2510-759 | Error count threshold has been exceeded, initiating recovery action(s). |
Explanation: A switch device has exceeded its error threshold. The switch recovery action will disable the faulty link or device.
User Response: If the switch device that the error threshold was exceeded for was not intentionally removed or powered off, then contact IBM Hardware service.
| 2510-760 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Incorrect EDC. |
Explanation: An EDC error has been detected by a switch chip. A likely cause for this error is that the device on the other side of the link has been powered down, reset, or rebooted. Other possible causes are that the data cable is faulty or not properly seated in the connectors. An EDC error indicated that data was corrupted when transmitted over a data link.
User Response: If this message continues to be logged, bring it to the attention of IBM Hardware service. For details, see the chapter on Diagnosing Switch Problems in PSSP: Diagnosis Guide.
| 2510-761 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Parity Error on Route. |
Explanation: A parity error has been detected on a route byte by the identified switch chip. A possible cause for the error is that there is noise on the specified link. Another likely cause is a problem in route generation.
User Response: Abnormal condition detected by hardware. Contact IBM Hardware service with the message number and text.
| 2510-762 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Undefined Control Char. |
Explanation: An Undefined Control Character has been detected by a switch chip. A likely cause for the error is that the device on the other side of the link has been powered down, reset, or rebooted. Other possible causes are that the data cable is faulty or not properly seated in the connectors.
User Response: If this message continues to be logged, bring it to the attention of IBM Hardware service.
| 2510-763 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Unsolicited Data. |
Explanation: Unsolicited Data has been detected by the identified switch chip.
User Response: Abnormal condition detected by hardware. Contact IBM Hardware service with the message number and text.
| 2510-764 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Receiver Lost EOP. |
Explanation: The loss of an End-of-Packet Character has been detected by the identified switch chip.
User Response: Abnormal condition detected by hardware. Contact IBM Hardware service with the message number and text.
| 2510-765 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. STI Route Violation. |
Explanation: A route violation has been detected on the identified switch.
User Response: Abnormal condition detected by hardware. Contact IBM Hardware service with the message number and text.
| 2510-766 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. STI Data Re-Time Req. |
Explanation: A STI Data Re_Time Request has been detected by the identified switch chip.
User Response: None. The message is informational.
| 2510-767 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Recv Link Sync Failure. |
Explanation: A Receiver Link Synchronization Failure has been detected by a switch chip. A likely cause for the error is that the device on the other side of the link has been powered down, reset, or rebooted. Other possible causes are that the data cable is faulty or not properly seated in the connectors.
User Response: Consult the section on Diagnosing Switch Problems in PSSP: Diagnosis Guide and check device on the other end of the link. If it was not intentionally powered off, rebooted or disconnected then contact IBM Hardware support.
| 2510-768 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. FIFO Overflow. |
Explanation: A FIFO overflow has occurred on the identified switch chip.
User Response: Abnormal condition detected by hardware. Contact IBM Hardware service with the message number and text.
| 2510-769 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Token Count Miscompare. |
Explanation: A Token Count Miscompare has been detected by the identified switch chip.
User Response: Abnormal condition detected by hardware. Contact IBM Hardware service with the message number and text.
| 2510-770 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. EDC Error Threshold. |
Explanation: An EDC Threshold Error has been detected by the chip. A likely cause for the error is that the device on the other side of the link has been powered down, reset, or rebooted.
Other possible causes are that the data cable is faulty or not properly seated in the connectors. This error indicates that the number of errors reported by a switch chip has exceeded its threshold. An EDC error indicates data was corrupted when transmitted over a link.
User Response: Consult section on Diagnosing Switch Problems in PSSP: Diagnosis Guide and check device on the other end of the link. If it wasn't intentionally powered off, rebooted or disconnected then contact IBM Hardware service.
| 2510-771 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Recv State Machine. |
Explanation: A receiver state machine error has been detected by the identified switch chip.
User Response: Abnormal condition detected by hardware. Contact IBM Hardware service with the message number and text.
| 2510-772 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Parity error on data. |
Explanation: A data parity error has been detected by the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-773 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Incorrect Token Seq. |
Explanation: An incorrect token sequence has been detected by the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-774 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Sender Invalid Route. |
Explanation: A An invalid route has been detected by the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-775 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Sender Lost EOP. |
Explanation: A lost End-of-Packet Character has been detected by the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-776 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. STI Token Re-Time Req. |
Explanation: An STI Token Re-Time Request has been detected by a switch chip. A likely cause for the error is that the device on the other side of the link has been powered down, reset, or rebooted.
User Response: None. The message is informational.
| 2510-777 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Token Count Overflow. |
Explanation: A token count overflow has occurred on the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-778 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Send Link Sync Failure. |
Explanation: A Sender link Synchronization Failure has been detected by a switch chip. A likely cause for the error is that the device on the other side of the link has been powered down, reset, or rebooted. Other possible causes are that the data cable is faulty or not properly seated in the connectors.
User Response: Consult section on Diagnosing Switch Problems in PSSP: Diagnosis Guide and check device on the other end of the link. If it wasn't intentionally powered off, rebooted or disconnected then contact IBM Hardware support.
| 2510-779 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Sender State Machine. |
Explanation: A sender state machine error has been detected by the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-780 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Next Message LL Parity. |
Explanation: A parity error has been detected on the next message linked list in the central queue by the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-781 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Next Chunk LL Parity. |
Explanation: A parity error has been detected on the next chunk linked list in the central queue by the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-782 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Next Chunk LL not Init. |
Explanation: The next chunk linked list in the central queue has not been initialized in the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-783 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Incorrect CRC. |
Explanation: An incorrect CRC has been detected on a service packet by the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-784 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Inbound FIFO Parity. |
Explanation: A parity error has been detected in the inbound FIFO on the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-785 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Route Table Parity. |
Explanation: A parity error has been detected in the route table by the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-786 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Invalid Link Enable. |
Explanation: An invalid link enable setting has been detected on the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-787 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Send TOD. |
Explanation: A switch chip received a service command to distribute its Time-of-Day value before it was valid.
User Response: Abnormal condition detected contact IBM Software Support.
| 2510-788 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Svc Logic State Machine. |
Explanation: A Service Logic State Machine error has been detected on the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-789 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Service Packet Length. |
Explanation: The identified switch chip received a service packet of incorrect length.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-790 | Error Capture Register (First or Second), location string (frame-slot-connector type-jack number), Chip and Port number. Token Error Threshold. |
Explanation: Token error threshold has been crossed on the identified switch chip.
User Response: Abnormal condition detected by switch hardware. Contact IBM Hardware service with the message number and text.
| 2510-791 | An Error/Status packet with no errors indicated was present by the switch in Frame, Slot, Chip, Port, Device ID. |
Explanation: An Error Status packet was received from a switch chip with no errors indicated. Device ID indicated has been cleared of errors.
User Response: None. The message is informational.
| 2510-792 | Port should have been in Disabled state. |
Explanation: The port is in an enabled state when it is expected to be disabled.
User Response: SP Switch Error Recovery has taken the appropriate action.
| 2510-793 | First Error Capture Register = First Error Capture Register |
Explanation: The SP Switch First Error Capture Register bits indicate which error condition was detected by the switch chip.
User Response: Review other messages logged in the flt near the time of this entry. The First Error Capture Register is used to report errors detected by the switch.
| 2510-798 | Disabling Switch Chip - Device ID=device id. |
Explanation: SP Switch chip with the specified device ID has been disabled. It is no longer an active part of the switch network. The chip either did not respond or report unrecoverable errors to the Primary fault service daemon. Switch traffic will be routed around the disabled chip.
User Response: Consult section on Diagnosing Switch Problems in PSSP: Diagnosis Guide.
| 2510-810 | Fault service daemon personality changed to Secondary. |
Explanation: The personality of the node's fault service daemon was changed to Secondary. Logging node no longer acting as switch Primary node.
User Response: None. The message is informational.
| 2510-811 | Fault service daemon's personality has been changed to Primary. |
Explanation: Fault service daemon's personality has been changed to Primary. This node is now acting as the Primary node. For a summary of current fault service daemon personalities, run Eprimary.
User Response: None. The message is informational.
| 2510-812 | Backup node starting as Primary node take-over. |
Explanation: The Primary Backup node has timed-out waiting for the Primary node to contact it. The Primary Backup is starting Primary node take-over.
User Response: None. The message is informational. Eprimary can be executed to find out which nodes are designated Primary and Backup.
| 2510-813 | Primary Backup node completed Primary node take-over. |
Explanation: Primary backup node has completed Primary node take-over and is now the Primary node. For a summary of current systems fault service daemon personalities, run Eprimary.
User Response: None. The message is informational. Eprimary can be executed to find out which nodes are designated Primary and Backup.
| 2510-814 | Port disable for fence of node node name completed. |
Explanation: The disabling of the switch port for fence has completed successfully.
User Response: None. The message is informational.
| 2510-815 | Port enable for unfence of node node name completed. |
Explanation: The enabling of the switch port for unfencing a node has completed successfully.
User Response: None. The message is informational.
| 2510-816 | Switch recovery timed-out waiting for an Error/Status packet from switch. Estart will be executed. |
Explanation: Switch recovery timed-out waiting for an Error/Status packet. Estart will be executed as a recovery action.
User Response: None, because a recovery action was taken. If the message continues to get logged, contact IBM Software Support.
| 2510-817 | A switch link or chip has been disabled internal to the network. Estart will be executed. |
Explanation: A switch link or chip has been disabled internal to the network. Estart will be executed as a recovery action. Estart will update switch routing tables to avoid using disabled link or chip.
User Response: None, because a recovery action was taken. If the message continues to get logged, contact IBM Software Support.
| 2510-818 | Switch Scan failed with a return code of return code. Estart will be executed. |
Explanation: The Primary fault service daemon periodically scans the switch network for errors. The scan detected a problem and as a result, Estart will be executed as a recovery action.
User Response: None, because a recovery action was taken. If the message continues to get logged, contact IBM Software Support.
| 2510-819 | Changing remote node's personality to be the Primary backup failed. Return code equals return code. Estart will be executed. |
Explanation: The Primary fault service daemon failed trying to change a node's personality to Primary backup. Estart will be executed.
User Response: None, because a recovery action was taken. If the message continues to get logged, contact IBM Software Support.
| 2510-820 | Primary's link to the switch network is not in the initialized state. |
Explanation: Estart found that the link to switch network was not initialized and was unable to run. The probable causes are that the node is fenced at the switch end of the link, the switch is improperly clocked, or the switch data cable is disconnected.
User Response: Use the Eprimary command to assign a new switch primary node then run Estart. If assigning a new primary does not work then running Eclock may fix the problem.
| 2510-821 | The second phase of the switch initialization will be retried. |
Explanation: The second phase of the switch initialization will be retried because of errors. The second phase of the switch initialization clears error bits and sets up service routes to the primary.
User Response: None. The message is informational.
| 2510-822 | The second phase of the switch initialization reached retry limit. Estart failed. |
Explanation: The second phase of switch initialization has reached it's retry limit. The second phase of the switch initialization clears error bits and sets up service routes to the primary. Estart failed.
User Response: Contact IBM Software Support.
| 2510-823 | The fault service daemon process has exited. |
Explanation: The fault service daemon process has exited.
User Response: Attempt to restart the fault service daemon by running /usr/lpp/ssp/css/rc.switch on the node. If the message continues to be logged contact IBM Software Support.
| 2510-824 | Switch initialization will be executed. |
Explanation: Switch initialization (Estart) will be executed.
User Response: None. The message is informational.
| 2510-825 | Retry limit exceeded for device ID=id. Disabling the device. |
Explanation: Retry limit for the device ID specified has exceeded the limit. The specified device will be disabled as a recovery action.
User Response: Contact IBM Hardware service.
| 2510-826 | Device id id uninitialized during switch initialization. Disabling the device. |
Explanation: The device ID specified was uninitialized during switch initialization. The specified device will be disabled as a recovery action.
User Response: None. The message is informational.
| 2510-827 | Unable to set Time-Of-Day for device ID id. Disabling the device. |
Explanation: Unable to set Time-Of-Day for the specified device. Device will be disabled as a recovery action.
User Response: None, because a recovery action was taken. If the message continues to be logged, contact IBM Software Support.
| 2510-828 | Error register bits found on device ID id. Disabling the device. |
Explanation: Error register bit were found for the specified device. Device will be disabled as a recovery action.
User Response: None, because a recovery action was taken. If the message continues to be logged, contact IBM Software Support.
| 2510-829 | Device ID id port port has been disabled. |
Explanation: The port on the device specified has been disabled because of an error reported by the link. This link will not be used.
User Response: None, because a recovery action was taken. If the message continues to be logged, contact IBM Software Support.
| 2510-830 | Switch port from Device device ID port mask 0x portmask stuck. |
Explanation: The specified device port did not go into disabled state. The most probable cause is that data remains in one of the ports specified in the port mask.
User Response: This is an abnormal condition detected by the primary fault service daemon. Record the above information and collect CSS snap dumps with the time of the failure from all nodes on the system. Contact the IBM Support Center.
| 2510-831 | Nodes attached to Device device ID not reachable for auto-join. |
Explanation: The nodes attached to the specified device can not be auto-joined because it is not initialized.
User Response: See /var/adm/SPlogs/css/flt and out.top files on the primary node for details on why the attached device is not initialized.
| 2510-832 | Node node id failed number of autojoin attempts consecutive autojoin attempts. The node put into the fenced-without-autojoin state. |
Explanation: The primary node attempted to autojoin a node a number of times until it reached a threshold. The node was then put into the fenced-without-autojoin state.
User Response: Check that the specified node is fully operational. If it is, collect the CSS snap dumps from the node, record the above information and contact the IBM Support Center.
| 2510-833 | Switch port from Device device ID port portmask stuck. |
Explanation: The specified device did not respond. The most probable cause is that data is stuck in one of the ports specified in the port mask.
User Response: This is an abnormal condition detected by the primary fault service daemon. Record the above information and collect CSS snap dumps with the time of the failure from all nodes on the system. Contact the IBM Support Center.
| 2510-834 | Node reliable hostname isolated because its switch port is stuck. |
Explanation: The specified node has been isolated because an error has been found on its switch port.
User Response: This is an abnormal condition detected by the primary fault service daemon. Record the above information and collect CSS snap dumps with the time of the failure from all nodes on the system. Contact the IBM Support Center.
| 2510-893 | Error found in handleFence(). |
Explanation: Fence failed to fence nodes.
User Response: See the section on Diagnosing Switch Problems in PSSP: Diagnosis Guide.
| 2510-894 | Error found in handleUnfence(). |
Explanation: Unfence failed to unfence nodes. Estart is executed as a recovery action.
User Response: See the section on Diagnosing Switch Problems in PSSP: Diagnosis Guide.
| 2510-897 | dist_to_bootservers failed during auto-unfence rc = errno. |
Explanation: The dist_to_bootservers command issued on the primary node returned a failing return code.
User Response: Examine the /var/adm/SPlogs/css/dist_topology.log file on the Primary node for reasons why the command failed.
| 2510-906 | Scan detected a problem with device device ID. |
Explanation: Scan detected a problem with the specified device. "Scan" periodically check the switch for unreported errors.
User Response: This is an abnormal condition detected by the fault service daemon. Record the above information and contact the IBM Support Center.
| 2510-913 | Resigning from being Primary node. |
Explanation: The Primary node was unable to scan the switch network. Therefore, it is resigning from being the Primary node and the Primary backup node will take over.
User Response: None. The message is informational.
| 2510-914 | Number of Node timeouts exceeded threshold. |
Explanation: Network Scan failed. It periodically checks the network for unreported errors.
User Response: An abnormal condition was detected by the fault service daemon. Record the above information and contact the IBM Support Center.
| 2510-915 | Number of Switch timeouts exceeded threshold. |
Explanation: Network scan failed because the number of errors found during scan exceeded the threshold. Network scan periodically checks the network for unreported errors.
User Response: An abnormal condition was detected by the fault service daemon Record the above information and contact the IBM Support Center.
| 2510-916 | Number of Errors discovered exceeded threshold. |
Explanation: Network scan failed because the number of errors found during the scan exceeded the threshold. Scan periodically checks the network for unreported errors.
User Response: Abnormal condition detected be fault service daemon, contact IBM Software Support with message number and text.
| 2510-917 | Number of disabled Links exceeded threshold. |
Explanation: Network scan failed because the number of disabled links found during scan exceeded the threshold.
User Response: Abnormal condition detected by fault service daemon, contact IBM Software Support with message number and text.
| 2510-918 | Interrupt Error Register = TB3 Interrupt Error Register. |
Explanation: The switch adapters Interrupt Error Register bits indicate which error conditions were detected by the adapter.
User Response: None. The message is informational.
| 2510-919 | Bad Device Signature detected. Device id = device ID. |
Explanation: A switch chip incorrect self-test signature was detected during switch initialization or recovery. Any new or replaced switch should be suspected of causing this error.
User Response: Abnormal condition, contact IBM Hardware service.
| 2510-921 | Timeout occurred waiting for pending Error/Status packet. |
Explanation: Timeout waiting for response from device, during switch recovery or initialization.
User Response: None, because a recovery action was taken. If the message continues to appear in the log, record the above information and contact the IBM Support Center.
| 2510-922 | Detected failure of intermediate port port number jack number of chip chip ID on the switch in slot slot number of frame frame number. |
Explanation: Switch recovery has detected a failure with a switch-to-switch link/port/cable. Estart is executed as a recovery action.
User Response: None, because a recovery action was taken. If the message continues to get logged, contact IBM Software Support.
| 2510-925 | Retry limit for Time-Of-Day synchronization exceeded. |
Explanation: Retry limit for Time-Of-Day synchronization exceeded. Switch clock may not be synchronized and switch is not initialized.
User Response: This is an abnormal condition. Record the above information and contact
IBM Hardware support.