Document: ER0363 Revised: 02/23/2001 Subject: 8229 Model 3 Error Messages Printable Version This tip applies to the following product(s): 8229 - -ALL- Message Product: Token-Ring Split Bridge (WAN) Logical Port 1 = Token-Ring Port Logical Port 2 = WAN Port Boot EPROM Diagnostic/Status Codes Blank Bridge Fully Functional 88 Lamp Test 00 - Processor Integrity Test 01 - Boot EPROM Checksum Test 02 - Control Processor Local SRAM Test 03 - Memory Size Determination/Check for minimum 04 - Window Register Check 05 - Parity Enable 06 - Lower 64K System RAM Diagnostics 07 - UART Test/Initialization, Timer Initialization 08 - not used 09 - Minimal Mode (invalid flash prom), awaiting download Motherboard Diagnostics 10 - Port Information Determination IPC Diagnostic Codes 11 - Forwarding Processor Alive Indication 12 - Interrupt to Forwarding Processor 13 - Interrupt from Forwarding Processor 14 - FP RAM Size Determination 15-18 - System RAM Tests 19 - Shadow RAM Test 20 - NVR Test 21 - AIP Test 22 - UART Test 29 - System Initialization 40 - Port 1 - Initialize 41 - Port 1 - Configure Bridge Channel 45 - Port 2 - Initialize internal register test 46 - Port 2 - Internal Loopback test 60 - Port 1 - Open Adapter 61 - Port 1 - Set Bridge Parameters 62 - Port 1 - Duplicate Address Test failed 63 - Port 1 - Unable to Open Adapter after one attempt (config mode only) 65 - Port 1 - WAN cable check 66 - Port 2 - External Loopback test 67 - Port 2 - WAN - Transmit Clock from modem/CSU test 68 - Port 2 - Major revision difference between bridge halves 94 - Port 1 - No MAU found 96 - Single Token-Ring port found. The unit is in minimal mode for downloading of code only. Runtime Status Codes 81 - Waiting for Initialization frame response from the other half 82 - Waiting for Configuration frame from Primary half 83 - Waiting for Adapter Info frame from the other half 84 - Waiting to receive the Start Test frame from the other half 85 - Ring numbers check 86 - Local Ring Test to ensure both adapters are not on the same ring 87 - Verify Bridge using Specific Route frames - Also verifies that parallel bridges have unique bridge numbers 88 - Verify Bridge using Broadcast frames 89 - No Communication from far half 91 - Receive clock from modem/DSU no longer present. 92 - Transmit clock from modem/DSU no longer present. 93 - WAN Cable was detached. Blank - Bridge Fully Functional The following messages may be displayed from the serial-port monitor. They give information about the Token-Ring Split bridge operation while it is running. In the first column, the hexadecimal number is the value of the alert that may be displayed through the serial port of the bridge. In the second column: W indicates that the alert is a "warning" and that the bridge will continue to operate without interruption. F indicates a failure alert issued just prior to restarting the bridge. Unless otherwise indicated, the message shown via the serial port will be "Inter-Bridge Error." The messages are organized by alert number. 0x0A49 (W) : The control processor received an unrecognized WAN frame from the forwarding processor. If this repeats, contact your support engineer. 0x0A4C (F) : Time-out waiting for bridge to transmit on the WAN. May be caused by (1) loss of transmit clock from modem/DSU, or (2) failure of forwarding processor. Upon automatic restart, the front panel will indicate the results of diagnostics in both of these areas. 0x0A4D (F) : Control processor ran out of internal control blocks. This message may occur as a side effect of a general failure, when the control processor receives a flood of frames from the network, but cannot transmit responses to them. Following the restart, diagnostics will indicate whether a persistent failure exists. 0x0A4E (F) : Control processor ran out of internal memory buffers. This message may occur as a side effect of a general failure, when the control processor receives a flood of frames from the network, but cannot transmit responses to them. Following the restart, diagnostics will indicate whether a persistent failure exists. 0x0A4F (F) : An internal queue is not empty, but has a zero count. If this repeats, contact your support engineer. 0x0A50 (F) : An internal queue is empty, but has a non-zero count. If this repeats, contact your support engineer. 0x0A51 (F) : An internal queue cannot receive another control block. If this repeats, contact your support engineer. 0x0A52 (W) : An invalid WAN receive state was detected. If this repeats, contact your support engineer. 0x0A53 (W) : When no forwarded frame traffic passes between the bridge halves, each half will send a "keep-alive" frame to the other side about every 4 seconds. When a bridge half receives a forwarded frame or a keep-alive frame, it "knows" that the other side is running, and that the communications line is operative. This alert is issued when no frame traffic of any kind has been received for 6 seconds. It indicates that the other half of the bridge has failed, or that the communication line has become inoperative. This alert is accompanied by a front panel LED display code of 89. If this alert repeats, and you have confirmed that the other half of the bridge is operative, then you should have your WAN service provider check the integrity of the communications line and/or modems. 0x0A54 (W) : The control processor received a WAN internal protocol frame that was not identified as a type 5, 6, or 7. If this repeats, contact your support engineer. 0x0A58 (W) : The control processor received the next internal protocol frame from the other side before it appears to have sent an ACK to the previous frame. This can theoretically occur during unusual conditions of heavy forwarding activity combined with lengthy control processor activity. If this repeats, contact your support engineer. 0x0A59 (W) : An unknown internal protocol frame type was received from the other side. If this repeats, contact your support engineer. 0x0A5A (W) : An invalid state was detected while sending an ACK for an internal protocol frame received from the other side. If this repeats, contact your support engineer. 0x0A5B (W) : An invalid state was detected while sending an internal protocol frame to the other side. If this repeats, contact your support engineer. 0x0A5C (W) : An attempt to send an internal protocol frame to the other side was abandoned after 10 tries at 2-second intervals failed to elicit an ACK from the other side. This can occur during sustained periods of forwarding activity that exceed the capacity of the bridge, combined with mildly degraded performance of the communication line. It may also occur as a result of a series of repetitive, lengthy noise bursts on the communications line. Generally, these conditions will also cause a Performance Threshold Exceeded alert to be issued to attached network managers. 0x0A5E (F) : An invalid state was detected during the initialization sequence. If this repeats, contact your support engineer. 0x0A5F (F) : Both sides of the bridge have been configured as the Primary side. When this occurs between two 8229s, the difference is resolved and no alert is issued. However, when one side is an IBM Token-Ring Remote Bridge (PC-based bridge), the 8229 must be configured as the Secondary. When this condition is detected, the 8229 will override the dip switch setting on the WAN adapter board, and restart itself as a Secondary. For future reliability, the dip switch should be changed to configure the 8229 as a Secondary. 0x0A60 (F) : The local side received an acknowledgment to its own initialization frame, but did not receive an initialization frame from the remote side. Intermittent failures in the communication path or in the remote bridge half may be causing the bridge halves to lose protocol synchronization during the start-up process. Repeated failures may indicate clock generation problems in DSUs used with point-to-point 4-wire cabling. Only one DSU should generate a clock, but both DSUs must use B8ZS encoding rather than AMI to ensure that clock signals may be recovered during times when the bridge is not transmitting data (as is the case just prior to the initialization sequence). 0x0A61 (F) : Time-out while sending the bridge configuration frame during the initialization sequence. If this repeats, contact your support engineer. 0x0A62 (F) : Time-out while waiting to receive the bridge configuration frame from the other side. If this repeats, contact your support engineer. 0x0A63 (F) : Time-out waiting for bridge to send a frame on the token ring. May have several external, ring-related causes, or forwarding processor may have failed. Upon automatic restart, the front panel will indicate the results of diagnostics in both of these areas. 0x0A64 (F) : Time-out waiting to receive the adapter information frame during the initialization sequence. If this repeats, contact your support engineer. 0x0A65 (F) : Initialization frames from both bridge halves had exactly the same time stamp. Generally this indicates that one of the modems or DSUs is set for Loopback test thus causing the bridge half to receive the same frame that it sends. In a test bench environment, this could also possibly happen if both halves of the bridge are controlled by a single power switch. 0x0A67 (W) : The network management LAN Reporting Mechanism has passed an invalid control block code to the WAN transmit module. If this repeats, contact your support engineer. 0x0A68 (W) : A frame being transmitted by the WAN returned an unknown status value. If this repeats, contact your support engineer. 0x0A69 (W) : The LAN Reporting Mechanism executed by the control processor has issued a split bridge initialization frame. If this repeats, contact your support engineer. 0x0A6A (W) : The LAN Reporting Mechanism executed by the control processor has issued a split bridge internal protocol frame during normal run-time operations. If this repeats, contact your support engineer. 0x0A6B (W) : The control processor attempted to queue an invalid internal protocol frame type for transmission on the WAN. If this repeats, contact your support engineer. 0x0A6E (W) : A spanning tree protocol frame generated by this 8229 does not contain a valid code point number. If this repeats, contact your support engineer. 0x0A6F (F) : During normal bridge operations, this half of the bridge received an initialization frame from the other side. This is assumed to indicate that the remote side has restarted, most likely as the result of a power interruption. Thus, this side of the bridge must also restart, in order to reestablish synchronization between the two sides. 0x0A70 (W) : A spanning tree protocol frame received from the other side does not contain a valid code point number. If this repeats, contact your support engineer. 0x0A71 (W) : An invalid state was detected in the periodic frame generation sequence. If this repeats, contact your support engineer. 0x0A72 (W) : The WAN local management appendage received a frame that was not an internal protocol frame. If this repeats, contact your support engineer. 0x0A73 (W) : The WAN local management appendage received an internal protocol frame with an invalid code point value. If this repeats, contact your support engineer. 0x0A74 (W) : Received an obsolete 0x000B internal protocol frame. If this repeats, contact your support engineer. 0x0A75 (W) : An invalid sub-system code was passed to the WAN function appendage. If this repeats, contact your support engineer. 0x0A76 (W) : In invalid code point request was passed to the WAN function appendage. If this repeats, contact your support engineer. 0x0A77 (W) : An invalid counters request frame was received from the secondary side. If this repeats, contact your support engineer. 0x0A78 (W) : The performance counter exchange protocol between the bridge halves detected an invalid state. The counters are exchanged once every minute. During periods of sustained bursts of forwarded frames (on the order of 20 seconds), it is possible for one side of the bridge to give up trying to exchange its counters with the other side. If the other side does not give up at approximately the same time, it will issue a frame that appears out of sequence to the receiving side. If this repeats, it indicates extremely high (at or over capacity) Token-Ring forwarding activity. 0x0A7A (W) : An invalid termination state was detected. This can occur during abnormal conditions when one side attempts to inform the other side that it is terminating. Some terminations are "gracefully" controlled, and others only attempt to be graceful in the presence of anomalous conditions. Generally, this alert will be followed by a restart that is caused by the other side restarting. If this message appears as part of a repeating restart situation, contact your support engineer. 0x0A7B (F) : Similar to 0x0A7A. A termination frame was received in a state where it was not expected. 0x0A7D (F) : A gracefully controlled termination sequence did not complete within the allowed time frame. See the remarks for 0x0A7A. 0x0A7E (W) : An inappropriate internal protocol frame type was passed to the LAN Reporting Mechanism. If this repeats, contact your support engineer. 0x0A7F (W) : An invalid major vector id number prevents the correct routing of a network management frame. If this repeats, contact your support engineer. 0x0A81 (W) : Internal protocol frame type 0x0010 has an adapter_id that is not 0. If this repeats, contact your support engineer. 0x0A87 (F) : Time-out waiting to send the start test frame during the initialization sequence. If this repeats, contact your support engineer. 0x0A88 (F) : Time-out waiting to receive the start test frame from the other side during the initialization sequence. If this repeats, contact your support engineer. 0x0A8A (F) : One side of the bridge contains IBM Network Management support, but the other side contains SNMP support. Reload both halves of the bridge with the same type and version of WAN operating software. 0x0A8E (W) : Internal protocol frame type 0x0011 frame size is too large. If this repeats, contact your support engineer. 0x0A90 (F) : The 8229 detects the presence of a cable on the WAN connector. However, the cable identification sense code does not match any supported cable type (EIA 232, X.21, or V.35). Check that the cable is one of the supported types, or replace the cable. 0x0A91 (W) : The ring numbers for the two halves of the bridge conflict in a way that prevents the bridge from becoming fully operational. The additional data provides information to help resolve the conflict: