From: VOELS@usmv01.usm.uni-muenchen.de (Stephen A. Voels)
Subject: Help with Error Log Entry
Organization: University Observatory Munich, FRG 
Date: Thu, 23 Jul 1992 16:17:40 GMT
X-News-Reader: VMS NEWS 1.20


     Maybe someone can help me interpret this error log entry or point me
in the right direction.

     First some background.  VMS 5.3-1. A 12 node VAXstation (5 x 3000's, 
7 x 2000's) VAXcluster.  When we make backups from the disks on one of the 
stations (VS 3200 with DELQA-M) to the Exabyte on the other (VS 3200 with
DELQA-M), the station with the disks tends to lose connections to the rest
of the cluster and then just sit there.  A backup to the NL: device (backup
running on the same machine as the Exabyte) does not seem to have this 
problem, but there is also no indication of any error problem with the 
Exabyte itself (ie. no error entry for the exabyte, only an error entry 
indicating that the connection to the machine with the disk has been lost).

     We first get an error log entry like ENTRY 7655 below.  This is then
followed by entries like ENTRY 7656 for each node in the cluster.  I have
initiated a system dump from the console a couple of times, but all I have
been able to determine is that CPU seems to be running around in the 
CLUSTRLOA area.

I hope somebody can help.

Stephen A. Voels


 ******************************* ENTRY    7655. *******************************
 ERROR SEQUENCE 31.                              LOGGED ON:        SID 0A000004
 DATE/TIME 21-JUL-1992 15:25:27.47                            SYS_TYPE 01120102
 SCS NODE: USMV02                                              VAX/VMS V5.3

 DEVICE ATTENTION  KA650  CPU REV# 5.  FW REV# 1.2

 NI-SCS SUB-SYSTEM, USMV02$PEA0:

       FATAL ERROR DETECTED BY DATALINK
 
       STATUS          0000002C
                       00000000
       DATALINK UNIT       0001
       DATALINK NAME   41515803
                       00000000
                       00000000
                       00000000
                                       DATALINK NAME = XQA1:
       REMOTE NODE     00000000
                       00000000
                       00000000
                       00000000
       REMOTE ADDR     00000000
                           0000
       LOCAL ADDR      000400AA
                           CC02
                                       ETHERNET ADDR = AA-00-04-00-02-CC
       ERROR CNT           0001
                                       1. ERROR OCCURRENCES THIS ENTRY
       UCB$W_ERRCNT        0001
                                       1. ERRORS THIS UNIT

 ******************************* ENTRY    7656. *******************************
 ERROR SEQUENCE 32.                              LOGGED ON:        SID 0A000004
 DATE/TIME 21-JUL-1992 15:25:37.45                            SYS_TYPE 01120102
 SCS NODE: USMV02                                              VAX/VMS V5.3

 ERL$LOGMESSAGE ENTRY  KA650  CPU REV# 5.  FW REV# 1.2

 NI-SCS SUB-SYSTEM, _USMV02$PEA0:

       PORT HAS CLOSED VIRTUAL CIRCUIT

       LOCAL STATION ADDRESS, FFFFFFFFFF00 (HEX)
       LOCAL SYSTEM ID, 00000000CC02 (HEX)

       REMOTE STATION ADDRESS, 0000000000D4 (HEX)
       REMOTE SYSTEM ID, 00000000CC03 (HEX)
 
       UCB$B_ERTCNT          32
                                       50. RETRIES REMAINING
       UCB$B_ERTMAX          32
                                       50. RETRIES ALLOWABLE
       UCB$W_ERRCNT        0002
                                       2. ERRORS THIS UNIT
       PPD$B_PORT            00
                                       REMOTE NODE #0.
       PPD$B_STATUS          00
       PPD$B_OPC             00
                                       PORT COMMAND, 0.
       PPD$B_FLAGS           00


Stephen A. Voels
Uni.-Sternwarte Muenchen     Internet:  voels@usm.uni-muenchen.de
Scheinerstr. 1               Voice:     +49-89-92209437
8000 Muenchen 80  FRG        FAX:       +49-89-92209427