|Document revision date: 15 July 2002|
Logged-message entries are made when the CI or LAN port receives a response that contains either data that the port driver cannot interpret or an error code in status field of the response.
Example C-8 shows a logged-message entry with an error code in the status field PPD$B_STATUS for a CI port.
|Example C-8 CI Port Logged-Message Entry|
************************* ENTRY 3. *************************** (1) ERROR SEQUENCE 3. LOGGED ON SID 01188542 ERL$LOGMESSAGE, 15-JAN-1994 13:40:25.13 (2) KA780 REV #3. SERIAL #1346. MFG PLANT 15. (3) CI SUB-SYSTEM, MARS$PAA0: (4) DATA CABLE(S) STATE CHANGE - PATH #0. WENT FROM GOOD TO BAD (5) LOCAL STATION ADDRESS, 000000000002 (HEX) (6) LOCAL SYSTEM ID, 000000000001 (HEX) (7) REMOTE STATION ADDRESS, 000000000004 (HEX) (8) REMOTE SYSTEM ID, 0000000000A9 (HEX) (9) UCB$B_ERTCNT 32 (10) 50. RETRIES REMAINING UCB$B_ERTMAX 32 50. RETRIES ALLOWABLE UCB$W_ERRCNT 0001 1. ERRORS THIS UNIT PPD$B_PORT 04 (11) REMOTE NODE #4. PPD$B_STATUS A5 (12) FAIL PATH #0., NO RESPONSE PATH #1., "ACK" OR NOT USED NO PATH PPD$B_OPC 05 (13) IDREQ PPD$B_FLAGS 03 (14) RESPONSE QUEUE BIT SELECT PATH #0. "CI" MESSAGE (15) 00000000 00000000 80000004 0000FE15 4F503000 00000507 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
The following table describes the logged-message entries in Example C-8.
|(1)||The first two lines are the entry heading. These lines contain the number of the entry in this error log file, the sequence number of the error, and the identification number (SID) of the computer. Each entry in the log file contains a heading.|
|(2)||This line contains the entry type, the date, and the time.|
|(3)||This line contains the processor type (KA780), the hardware revision number of the computer (REV #3), the serial number of the computer (SERIAL #1346), and the plant number (15).|
|(4)||This line shows the name of the subsystem and the device that caused the entry.|
This line gives the reason for the entry (one or more data cables have
changed state) and a more detailed reason for the entry. Path 0, which
the port used successfully before, cannot be used now.
Note: ANALYZE/ERROR_LOG uses the notation "path 0" and "path 1"; cable labels use the notation "path A (=0)" and "path B (=1)".
|(6)||The local ((6)) and remote ((8)) station addresses are the port numbers (range 0 to 15) of the local and remote ports. The port numbers are set in hardware switches by Compaq support representatives.|
|(7)||The local ((7)) and remote ((9)) system IDs are the SCS system IDs set by the system parameter SCSSYSTEMID for the local and remote systems. For HSC subsystems, the system ID is set with the HSC console.|
|(10)||The next three lines consist of the entry fields that begin with UCB$. These fields give information on the contents of the unit control block (UCB) for this CI device.|
|(11)||The lines that begin with PPD$ are fields in the message packet that the local port has received. PPD$B_PORT contains the station address of the remote port. In a loopback datagram, however, this field contains the local station address.|
|(12)||The PPD$B_STATUS field contains information about the nature of the failure that occurred during the current operation. When the operation completes without error, ERF prints the word NORMAL beside this field; otherwise, ERF decodes the error information contained in PPD$B_STATUS. Here a NO PATH error occurred because of a lack of response on path 0, the selected path.|
|(13)||The PPD$B_OPC field contains the code for the operation that the port was attempting when the error occurred. The port was trying to send a request-for-ID message.|
|(14)||The PPD$B_FLAGS field contains bits that indicate, among other things, the path that was selected for the operation.|
|(15)||"CI" MESSAGE is a hexadecimal listing of bytes 16 through 83 (decimal) of the response (message or datagram). Because responses are of variable length, depending on the port opcode, bytes 16 through 83 may contain either more or fewer bytes than actually belong to the message.|
This section describes error-log entries for the CI and LAN ports. Each entry shown is followed by a brief description of what the associated port driver (for example, PADRIVER, PBDRIVER, PEDRIVER) does, and the suggested action a system manager should take. In cases where you are advised to contact your Compaq support representative. and save crash dumps, it is important to capture the crash dumps as soon as possible after the error. For CI entries, note that path A and path 0 are the same path, and that path B and path 1 are the same path.
Table C-6 lists error-log messages.
|BIIC FAILURE||The port driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line.||Contact your Compaq support representative.|
|CI PORT TIMEOUT||The port driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line.||Increase the PAPOLLINTERVAL system parameter. If the problem disappears and you are not running privileged user-written software, contact your Compaq support representative.|
|11/750 CPU MICROCODE NOT ADEQUATE FOR PORT||The port driver sets the port off line with no retries attempted. In addition, if this port is needed because the computer is booted from an HSC subsystem or is participating in a cluster, the computer bugchecks with a UCODEREV code bugcheck.||Read the appropriate section in the current OpenVMS Cluster Software SPD for information on required computer microcode revisions. Contact your Compaq support representative, if necessary.|
|PORT MICROCODE REV NOT CURRENT, BUT SUPPORTED||The port driver detected that the microcode is not at the current level, but the port driver will continue normally. This error is logged as a warning only.||Contact your Compaq support representative when it is convenient to have the microcode updated.|
|PORT MICROCODE REV NOT SUPPORTED||The port driver sets the port off line without attempting any retries.||Read the OpenVMS Cluster Software SPD for information on the required CI port microcode revisions. Contact your Compaq support representative, if necessary.|
|DATA CABLE(S) STATE CHANGE\CABLES HAVE GONE FROM CROSSED TO UNCROSSED||The port driver logs this event.||No action needed.|
|DATA CABLE(S) STATE CHANGE\CABLES HAVE GONE FROM UNCROSSED TO CROSSED||The port driver logs this event.||Check for crossed cable pairs. (See Section C.10.5.)|
|DATA CABLE(S) STATE CHANGE\PATH 0. WENT FROM BAD TO GOOD||The port driver logs this event.||No action needed.|
|DATA CABLE(S) STATE CHANGE\PATH 0. WENT FROM GOOD TO BAD||The port driver logs this event.||Check path A cables to see that they are not broken or improperly connected.|
|DATA CABLE(S) STATE CHANGE\PATH 0. LOOPBACK IS NOW GOOD, UNCROSSED||The port driver logs this event.||No action needed.|
|DATA CABLE(S) STATE CHANGE\PATH 0. LOOPBACK WENT FROM GOOD TO BAD||The port driver logs this event.||Check for crossed cable pairs or faulty CI hardware. (See Sections C.10.3 and C.10.5.)|
|DATA CABLE(S) STATE CHANGE\PATH 1. WENT FROM BAD TO GOOD||The port driver logs this event.||No action needed.|
|DATA CABLE(S) STATE CHANGE\PATH 1. WENT FROM GOOD TO BAD||The port driver logs this event.||Check path B cables to see that they are not broken or improperly connected.|
|DATA CABLE(S) STATE CHANGE\PATH 1. LOOPBACK IS NOW GOOD, UNCROSSED||The port driver logs this event.||No action needed.|
|DATA CABLE(S) STATE CHANGE\PATH 1. LOOPBACK WENT FROM GOOD TO BAD||The port driver logs this event.||Check for crossed cable pairs or faulty CI hardware. (See Sections C.10.3 and C.10.5.)|
|DATAGRAM FREE QUEUE INSERT FAILURE||The port driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line.||Contact your Compaq support representative. This error is caused by a failure to obtain access to an interlocked queue. Possible sources of the problem are CI hardware failures, or memory, SBI (11/780), CMI (11/750), or BI (8200, 8300, and 8800) contention.|
|DATAGRAM FREE QUEUE REMOVE FAILURE||Contact your Compaq support representative. This error is caused by a failure to obtain access to an interlocked queue. Possible sources of the problem are CI hardware failures, or memory, SBI (11/780), CMI (11/750), or BI (8200, 8300, and 8800) contention.|
|FAILED TO LOCATE PORT MICROCODE IMAGE||The port driver marks the device off line and makes no retries.||Make sure console volume contains the microcode file CI780.BIN (for the CI780, CI750, or CIBCI) or the microcode file CIBCA.BIN for the CIBCA--AA. Then reboot the computer.|
|HIGH PRIORITY COMMAND QUEUE INSERT FAILURE||Contact your Compaq support representative. This error is caused by a failure to obtain access to an interlocked queue. Possible sources of the problem are CI hardware failures, or memory, SBI (11/780), CMI (11/750), or BI (8200, 8300, and 8800) contention.|
|MSCP ERROR LOGGING DATAGRAM RECEIVED||On receipt of an error message from the HSC subsystem, the port driver logs the error and takes no other action. You should disable the sending of HSC informational error-log datagrams with the appropriate HSC console command because such datagrams take considerable space in the error-log data file.||Error-log datagrams are useful to read only if they are not captured on the HSC console for some reason (for example, if the HSC console ran out of paper.) This logged information duplicates messages logged on the HSC console.|
|INAPPROPRIATE SCA CONTROL MESSAGE||The port driver closes the port-to-port virtual circuit to the remote port.||Contact your Compaq support representative. Save the error logs and the crash dumps from the local and remote computers.|
|INSUFFICIENT NON-PAGED POOL FOR INITIALIZATION||The port driver marks the device off line and makes no retries.||Reboot the computer with a larger value for NPAGEDYN or NPAGEVIR.|
|LOW PRIORITY CMD QUEUE INSERT FAILURE|
|MESSAGE FREE QUEUE INSERT FAILURE|
|MESSAGE FREE QUEUE REMOVE FAILURE|
|MICRO-CODE VERIFICATION ERROR||The port driver detected an error while reading the microcode that it just loaded into the port. The driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line.||Contact your Compaq support representative.|
|NO PATH-BLOCK DURING VIRTUAL CIRCUIT CLOSE||Contact your Compaq support representative. Save the error log and a crash dump from the local computer.|
|NO TRANSITION FROM UNINITIALIZED TO DISABLED||Contact your Compaq support representative.|
|PORT ERROR BIT(S) SET||A maintenance timer expiration bit may mean that the PASTIMOUT system parameter is set too low and should be increased, especially if the local computer is running privileged user-written software. For all other bits, call your Compaq support representative.|
|PORT HAS CLOSED VIRTUAL CIRCUIT||The port driver closed the virtual circuit that the local port opened to the remote port.||
Check the PPD$B_STATUS field of the error-log entry for the reason the
virtual circuit was closed. This error is normal if the remote computer
failed or was shut down. For PEDRIVER, ignore the PPD$B_OPC field
value; it is an unknown opcode.
If PEDRIVER logs a large number of these errors, there may be a problem either with the LAN or with a remote system, or nonpaged pool may be insufficient on the local system.
|PORT POWER DOWN||The port driver halts port operations and then waits for power to return to the port hardware.||Restore power to the port hardware.|
|PORT POWER UP||The port driver reinitializes the port and restarts port operations.||No action needed.|
|RECEIVED CONNECT WITHOUT PATH-BLOCK||Contact your Compaq support representative. Save the error log and a crash dump from the local computer.|
|REMOTE SYSTEM CONFLICTS WITH KNOWN SYSTEM||The configuration poller discovered a remote computer with SCSSYSTEMID and/or SCSNODE equal to that of another computer to which a virtual circuit is already open.||Shut down the new computer as soon as possible. Reboot it with a unique SCSYSTEMID and SCSNODE. Do not leave the new computer up any longer than necessary. If you are running a cluster, and two computers with conflicting identity are polling when any other virtual circuit failure takes place in the cluster, then computers in the cluster may shut down with a CLUEXIT bugcheck.|
|RESPONSE QUEUE REMOVE FAILURE|
|SCSSYSTEMID MUST BE SET TO NON-ZERO VALUE||The port driver sets the port off line without attempting any retries.||Reboot the computer with a conversational boot and set the SCSSYSTEMID to the correct value. At the same time, check that SCSNODE has been set to the correct nonblank value.|
|SOFTWARE IS CLOSING VIRTUAL CIRCUIT||The port driver closes the virtual circuit to the remote port.||Check error-log entries for the cause of the virtual circuit closure. Faulty transmission or reception on both paths, for example, causes this error and may be detected from the one or two previous error-log entries noting bad paths to this remote computer.|
|SOFTWARE SHUTTING DOWN PORT||Check other error-log entries for the possible cause of the port reinitialization failure.|
|UNEXPECTED INTERRUPT||Contact your Compaq support representative.|
|UNRECOGNIZED SCA PACKET||The port driver closes the virtual circuit to the remote port. If the virtual circuit is already closed, the port driver inhibits datagram reception from the remote port.||Contact your Compaq support representative. Save the error-log file that contains this entry and the crash dumps from both the local and remote computers.|
|VIRTUAL CIRCUIT TIMEOUT||The port driver closes the virtual circuit that the local CI port opened to the remote port. This closure occurs if the remote computer is running CI microcode Version 7 or later, and if the remote computer has failed to respond to any messages sent by the local computer.||This error is normal if the remote computer has halted, failed, or was shut down. This error may mean that the local computer's TIMVCFAIL system parameter is set too low, especially if the remote computer is running privileged user-written software.|
|INSUFFICIENT NON-PAGED POOL FOR VIRTUAL CIRCUITS||The port driver closes virtual circuits because of insufficient pool.||Enter the DCL command SHOW MEMORY to determine pool requirements, and then adjust the appropriate system parameter requirements.|
The descriptions in Table C-7 apply only to LAN devices.
|Message||Completion Status||Explanation||User Action|
|FATAL ERROR DETECTED BY DATALINK||First longword SS$_NORMAL (00000001), second longword (00001201)||The LAN driver stopped the local area OpenVMS Cluster protocol on the device. This completion status is returned when the SYS$LAVC_STOP_BUS routine completes successfully. The SYS$LAVC_STOP_BUS routine is called either from within the LAVC$STOP_BUS.MAR program found in SYS$EXAMPLES or from a user-written program. The local area OpenVMS Cluster protocol remains stopped on the specified device until the SYS$LAVC_START_BUS routine executes successfully. The SYS$LAVC_START_BUS routine is called from within the LAVC$START_BUS.MAR program found in SYS$EXAMPLES or from a user-written program.||
If the protocol on the device was stopped inadvertently, then restart
the protocol by assembling and executing the LAVC$START_BUS program
found in SYS$EXAMPLES.
Reference: See Appendix D for an explanation of the local area OpenVMS Cluster sample programs. Otherwise, this error message can be safely ignored.
|First longword is any value other than (00000001), second longword (00001201)||The LAN driver has shut down the device because of a fatal error and is returning all outstanding transmits with SS$_OPINCOMPL. The LAN device is restarted automatically.||Infrequent occurrences of this error are typically not a problem. If the error occurs frequently or is accompanied by loss or reestablishment of connections to remote computers, there may be a hardware problem. Check for the proper LAN adapter revision level or contact your Compaq support representative.|
|First longword (undefined), second longword (00001200)||The LAN driver has restarted the device successfully after a fatal error. This error-log message is usually preceded by a FATAL ERROR DETECTED BY DATALINK error-log message whose first completion status longword is anything other than 00000001 and whose second completion status longword is 00001201.||No action needed.|
|TRANSMIT ERROR FROM DATALINK||SS$_OPINCOMPL (000002D4)||The LAN driver is in the process of restarting the data link because an error forced the driver to shut down the controller and all users (see FATAL ERROR DETECTED BY DATALINK).|
|SS$_DEVREQERR (00000334)||The LAN controller tried to transmit the packet 16 times and failed because of defers and collisions. This condition indicates that LAN traffic is heavy.|
|SS$_DISCONNECT (0000204C)||There was a loss of carrier during or after the transmit.||The port emulator automatically recovers from any of these errors, but many such errors indicate either that the LAN controller is faulty or that the LAN is overloaded. If you suspect either of these conditions, contact your Compaq support representative.|
|INVALID CLUSTER PASSWORD RECEIVED||A computer is trying to join the cluster using the correct cluster group number for this cluster but an invalid password. The port emulator discards the message. The probable cause is that another cluster on the LAN is using the same cluster group number.||Provide all clusters on the same LAN with unique cluster group numbers.|
|NISCS PROTOCOL VERSION MISMATCH RECEIVED||A computer is trying to join the cluster using a version of the cluster LAN protocol that is incompatible with the one in use on this cluster.||Install a version of the operating system that uses a compatible protocol, or change the cluster group number so that the computer joins a different cluster.|
|privacy and legal statement|