| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 908.1 | Update.... | YODA::JEAN | MAUREEN JEAN | Fri Mar 26 1993 16:49 | 8 |
|
The DEMFA code looks like it is 1.0 not 1.4. There
are quite a few problems that were fixed between these
revs.
Maureen
|
| 908.2 | Same Problem is/was there a solution | HLFS00::EITENS_S | Sieds Eitens C.S. Hoogeveen | Wed Jan 19 1994 09:27 | 7 |
| I have a customer who has the same problem as mentioned in 908.0
could somebody tell me what the solutiom was or if the problem is
solved.
Regards Sieds Eitens
MCS Hoogeveen Holland.
|
| 908.3 | Need more info.... | PROXY::JEAN | MAUREEN JEAN | Fri Jan 21 1994 15:18 | 10 |
|
The base noter was running with 1.0 of the code. Is this what
your customer has? Can you provide the error logs so I can take
a look?
Thanks,
Maureen
|
| 908.4 | More info 908.2 | HLFS00::EITENS_S | Sieds Eitens C.S. Hoogeveen | Mon Jan 24 1994 04:37 | 106 |
| Maureen,
Here is the errorlog entry and it looks to me that its running 1.4
firmware using VMS 5.4-3.
An other remark is that the XMI from this machine is very loaded, but
at this moment i haven't got a compleet config if you need it just let
me know bellow i have list the amount of XMI modules but i haven't got
an configuration how they are placed in the machine.
About half a year a go the same problem occured and then the DEMFA was
replaced, the senario was the same. The complaint of the customer is
that he is using host based shadowing and when the DEMFA fails it
reinitializes and restarts again starting shadow copies from all
shadowed disks. From the moment that this happend until now, about a
week later, the whole thing is running fine.
The XMI config at this moment is
2 X KA64 2 modules
4 x MS62a 32 mb 4 modules
1 x MS65a 64 mb 1 module
2 x KFMSA 2 modules
1 x KDM70 2 modules
1 x DWMBB-DA only one BI 1 module
1 x DEMFA 1 module
total 13 modules on the XMI
On the BI is a module from a third party which makes a "fast"
connection with a UNISYS mainframe.
DEMFA SUB-SYSTEM, VAX008$FXA0:
ERROR TYPE CODE #8., ERROR SUBTYPE CODE #35.
XDEV REG 05140823
DEVICE TYPE = 0823(X)
FIRMWARE REV = 14(X)
HARDWARE REV = 05(X)
PORT STATUS REG 000F200D
HALTED STATE
LED STATE = 04(X)
FATAL HARDWARE INTERNAL ERROR
FDDI RING AVAILABLE
XPUD REG 80000018
RESET COUNT 0000
FIRMWARE REV 14
ERROR REASON 03
TIME STAMP 12A20000A200
11. HRS, 31. MINS, 12. SECS
WRITE COUNT 0003
MSGID 00000203
USRDEF0 01200000
USRDEF1 00000400
USRDEF2 00000001
PARICR 00000000
PMCCSR0 22002003
REM ENABLE
REM FREEZE
RMC DISCARD XMT-WRITE TRANSAC.
MEMORY MANAGEMENT ENABLE
PMCCSR1 02700F00
PMCCSR2 01200000
MASK AM DEST PKT DISC INTRRPT
MASK HOST DEST PKT DISC INTRPT
PMCCSR3 00000000
ESP ERROR REG 00000400
XMI ERROR
XBE C000A0C0
XFADR 14862C00
XFAER 10010000
XPUD REG 80000018
SELF-TEST COMPLETE
NORMAL MODE
NO FRU FAILURE
GPCSR 00000400
CLEAR OWNERSHIP ENABLED
INTCSR1 00000000
INTCSR2 00000400
AMIR 00000001
ESP ERR REG BITS ARE SET
VBR 00200000
CAAR 0000000C
CACR 00000001
DFC 00000007
SFC 00000007
UCB$B_ERTCNT 14
20. RETRIES REMAINING
UCB$B_ERTMAX 05
5. RETRIES ALLOWABLE
UCB$L_CHAR 0C442000
NETWORK
AVAILABLE
ERROR LOGGING
CAPABLE OF INPUT
CAPABLE OF OUTPUT
UCB$W_STS 2010
ONLINE
UCB$W_ERRCNT 0001
1. ERRORS THIS UNIT
At RDC they came up with the conclusion that the DEMFA was adressing
somewhere around 344 MB in memory,but the machine doesn't have that
amount of memory is has 192 mb.
As i understand it from the base note there isn't a clear solution or
wat solved the problem in that case.
Maureen thanks for the time that you are spending, and hope to
hear "read" from you soon again.
Regards Sieds Eitens
MCS Hoogeveen Holland.
|
| 908.5 | Any Progres ???? | HLFS00::EITENS_S | Sieds Eitens MCS Hoogeveen Holland | Mon Feb 07 1994 04:53 | 8 |
| Maureen,
Is there an progres about this problem, because i have to give an
answer to the cusomer.
So if you have some info i would really appriciate it.
Regards Sieds.
|
| 908.6 | It happend sooner again.!!! | HLFS00::EITENS_S | Sieds Eitens MCS Hoogeveen Holland | Fri Feb 11 1994 14:09 | 6 |
| It happend again within a month, with the same senario. We have decided
to upgrade the firmware on de DEMFA from 1.4 to 2.0 this is planned for
next week. Keep you posted wat happens.
Regards Sieds.
|
| 908.7 | What is a INTERNAL error 8?????? | HLFS00::EITENS_S | Sieds Eitens MCS Hoogeveen Holland | Tue Feb 15 1994 04:12 | 9 |
| Could someone give us some info about this internal error 8
on a DEMFA, because when reading note 1229 the same problem seems to
appear with VMS 5.5-2 and the firmware rev from the DEMFA on 2.0.
So the action we have planned at the moment, upgrading the firmware,
doesn't seem to solve the problem.
Regards Sieds Eitens
MCS Hoogeveen.
|
| 908.8 | | NETRIX::thomas | The Code Warrior | Tue Feb 15 1994 09:55 | 1 |
| My DEMFA specs stops at 7.
|
| 908.9 | Same problems in note 1229 | HLFS00::EITENS_S | Sieds Eitens MCS Hoogeveen Holland | Wed Feb 16 1994 03:55 | 1 |
| The same problems came up in note 1229 so read that one aswell.
|
| 908.10 | It happend again in about 6 month. | HLFS00::EITENS_S | Sieds Eitens MCS Hoogeveen Holland | Tue Aug 23 1994 09:59 | 172 |
| Maureen,
You shouldn't have reacted on this entry in the notesfile, a few days after
you've mail to say your sorry about the responce it happend again at the
customer site. Even twice. Before 19-aug-1994 it happend on the 28-jan-1994,
the entry in the notesfel, and on the 22-aug-1994 both latest errorlog entries
are included in this mail.
For early info it is stil in the notesfile and there hasn't been any changes
execpt the VMS update.
The things what have changed between febraury and now is that they have updated
VMS from 5.4-3 to 5.5-2. The FXdriver is at level X20.
We have adviced the customer to update the Fxdriver to X22 but on what reason
so ever they didn't do it.
So my question is can you give your idear about this problem and what action we
can take or advice to the customer.
DATE 19-AUG-1994 15:06:06.62
DEMFA SUB-SYSTEM, VAX008$FXA0:
ERROR TYPE CODE #8., ERROR SUBTYPE CODE #35.
XDEV REG 05140823
DEVICE TYPE = 0823(X)
FIRMWARE REV = 14(X)
HARDWARE REV = 05(X)
PORT STATUS REG 000F200D
HALTED STATE
LED STATE = 04(X)
FATAL HARDWARE INTERNAL ERROR
FDDI RING AVAILABLE
XPUD REG 80000018
RESET COUNT 0000
FIRMWARE REV 14
ERROR REASON 03
TIME STAMP 08630000DD00
15. HRS, 42. MINS, 56. SECS
WRITE COUNT 0004
MSGID 00000203
USRDEF0 01200000
USRDEF1 00000400
USRDEF2 00000001
PARICR 00000000
PMCCSR0 22002003
REM ENABLE
REM FREEZE
RMC DISCARD XMT-WRITE TRANSAC.
MEMORY MANAGEMENT ENABLE
PMCCSR1 8F150000
PMCCSR2 01200000
MASK AM DEST PKT DISC INTRRPT
MASK HOST DEST PKT DISC INTRPT
PMCCSR3 00000000
ESP ERROR REG 00000400
XMI ERROR
XBE C000A0C0
XFADR 15C84E00
XFAER 10010000
XPUD REG 80000018
SELF-TEST COMPLETE
NORMAL MODE
NO FRU FAILURE
GPCSR 00000400
CLEAR OWNERSHIP ENABLED
INTCSR1 00200000
INTCSR2 00000400
AMIR 00000001
ESP ERR REG BITS ARE SET
VBR 00200000
CAAR 0000000C
CACR 00000001
DFC 00000007
SFC 00000007
UCB$B_ERTCNT 14
20. RETRIES REMAINING
UCB$B_ERTMAX 05
5. RETRIES ALLOWABLE
UCB$L_CHAR 0C442000
NETWORK
AVAILABLE
ERROR LOGGING
CAPABLE OF INPUT
CAPABLE OF OUTPUT
UCB$W_STS 2010
ONLINE
UCB$W_ERRCNT 0001
1. ERRORS THIS UNIT
DATE 22-AUG-1994 15:49:41
DEMFA SUB-SYSTEM, VAX008$FXA0:
ERROR TYPE CODE #8., ERROR SUBTYPE CODE #35.
XDEV REG 05140823
DEVICE TYPE = 0823(X)
FIRMWARE REV = 14(X)
HARDWARE REV = 05(X)
PORT STATUS REG 000F200D
HALTED STATE
LED STATE = 04(X)
FATAL HARDWARE INTERNAL ERROR
FDDI RING AVAILABLE
XPUD REG 80000018
RESET COUNT 0000
FIRMWARE REV 14
ERROR REASON 03
TIME STAMP 026100001200
1. HRS, 16. MINS, 48. SECS
WRITE COUNT 0004
MSGID 00000203
USRDEF0 01200000
USRDEF1 00000400
USRDEF2 00000001
PARICR 00000000
PMCCSR0 22002003
REM ENABLE
REM FREEZE
RMC DISCARD XMT-WRITE TRANSAC.
MEMORY MANAGEMENT ENABLE
PMCCSR1 8D080000
PMCCSR2 01200000
MASK AM DEST PKT DISC INTRRPT
MASK HOST DEST PKT DISC INTRPT
PMCCSR3 00000000
ESP ERROR REG 00000400
XMI ERROR
XBE C000A0C0
XFADR 15C1AA00
XFAER 10010000
XPUD REG 80000018
SELF-TEST COMPLETE
NORMAL MODE
NO FRU FAILURE
GPCSR 00000400
CLEAR OWNERSHIP ENABLED
INTCSR1 00200000
IPF-FDDI MAC CHIP INTRPT PEND
INTCSR2 00000400
AMIR 00000001
ESP ERR REG BITS ARE SET
VBR 00200000
CAAR 0000000C
CACR 00000001
DFC 00000007
SFC 00000007
UCB$B_ERTCNT 14
20. RETRIES REMAINING
UCB$B_ERTMAX 05
5. RETRIES ALLOWABLE
UCB$L_CHAR 0C442000
NETWORK
AVAILABLE
ERROR LOGGING
CAPABLE OF INPUT
CAPABLE OF OUTPUT
UCB$W_STS 2010
ONLINE
UCB$W_ERRCNT 0002
2. ERRORS THIS UNIT
Hoping that you will find the time to answer this question this week.
Regards Sieds Eitens
MCS The Netherlands.
|
| 908.11 | Error type 8 on 7600 and 6600's | CSC32::B_KETELSEN | | Thu Oct 20 1994 14:25 | 15 |
| I also have a site which is reporting intermittant error type code 8
errors on their FXA0 devices. These errors are logged on both their
7000-600 and 6000-600 systems. The FXDriver is at version X-22A1
and VMS is at 5.5-2. The DEMFA cards are firmware rev 20,
hardware rev 5. The complete errorlog entry and/or configuration
information is available if needed.
When this error occurs, it causes some processes that use the FDDI to
either abort or report the device inactive, and because of this, it
is becoming a major problem. Has any solution for this problem been
found yet?
Thanks,
Bobbi Ketelsen
|
| 908.12 | Does your error look like this? | AKRON1::SMITH | Sic Semper Potatum Reclinus | Wed Nov 02 1994 15:46 | 106 |
|
RE .11
Here's an errorlog entry from a site from today....
Does this look like what you're seeing?
Is anyone in engineering concerned about this?
It seems to be happening quite a bit.
In my case, the DEMFA logged three of these within about 75 seconds
and started an avalanche that resulted in all satellite systems
CLUEXITing (about 60 workstations). As in .11, we're running VMS
5.5-2H4 and FXDRIVER is at X-22A1 and the DEFMA is firmware rev 20.
...the only difference is my DEFMA hardware rev shows up as 00.
Jeff Smith
OVD Support Center
Cleveland, Ohio
DTN 431-2712
The errlog entry is as follows:
V A X / V M S SYSTEM ERROR REPORT COMPILED 2-NOV-1994 12:48:22
PAGE 1.
******************************* ENTRY 458. *******************************
ERROR SEQUENCE 33823. LOGGED ON: SID 17000202
DATE/TIME 2-NOV-1994 09:22:51.13 SYS_TYPE 01030001
SYSTEM UPTIME: 10 DAYS 22:29:26
SCS NODE: SUM VAX/VMS V5.5-2H4
DEVICE ATTENTION KA7AA-AA CPU FW REV# 2. CONSOLE FW REV# 0.3
DEMFA SUB-SYSTEM, SUM$FXA0:
ERROR TYPE CODE #8., ERROR SUBTYPE CODE #35.
XDEV REG 00200823
DEVICE TYPE = 0823(X)
FIRMWARE REV = 20(X)
HARDWARE REV = 00(X)
PORT STATUS REG 000F200D
HALTED STATE
LED STATE = 04(X)
FATAL HARDWARE INTERNAL ERROR
FDDI RING AVAILABLE
XPUD REG 80000018
RESET COUNT 0000
FIRMWARE REV 20
ERROR REASON 03
TIME STAMP 088A0000C280
13. HRS, 49. MINS, 52. SECS
WRITE COUNT 0007
MSGID 00000203
USRDEF0 01200000
USRDEF1 00000040
USRDEF2 00000001
PARICR 00000000
PMCCSR0 2200A003
REM ENABLE
REM FREEZE
RMC DISCARD XMT-WRITE TRANSAC.
REM FORCE TRANSMIT PRIORITY
MEMORY MANAGEMENT ENABLE
PMCCSR1 899B0000
PMCCSR2 01200000
MASK AM DEST PKT DISC INTRRPT
MASK HOST DEST PKT DISC INTRPT
PMCCSR3 00000000
ESP ERROR REG 00000040
XMI BYTE COUNT ERROR
XBE 0000004A
XFADR C01382B0
XFAER 10000000
XPUD REG 80000018
SELF-TEST COMPLETE
NORMAL MODE
NO FRU FAILURE
GPCSR 00000400
CLEAR OWNERSHIP ENABLED
INTCSR1 00000000
INTCSR2 00000400
AMIR 00000001
ESP ERR REG BITS ARE SET
VBR 00200000
CAAR 0000000C
CACR 00000001
DFC 00000007
SFC 00000007
UCB$B_ERTCNT 20
32. RETRIES REMAINING
UCB$B_ERTMAX 00
0. RETRIES ALLOWABLE
UCB$L_CHAR 0C442000
NETWORK
AVAILABLE
ERROR LOGGING
CAPABLE OF INPUT
CAPABLE OF OUTPUT
UCB$W_STS 2010
ONLINE
UCB$W_ERRCNT 0003
3. ERRORS THIS UNIT
|
| 908.13 | ERROR 8 | PROXY::JEAN | MAUREEN JEAN | Thu Nov 03 1994 12:15 | 22 |
|
I took some of this offline and I probably shouldn't have because
I may have caused more confusion.
Let me first state that error 8 is not one particular error.
It is many differnet errors, and that was one of the reasons I
did take it off line. If I remember correctly, the first few
entries in this note all had different problems. So yes,
engineering is doing something about all these problems. Some
of them have fixes and some of them we are working. So please
don't assume that it is all the same problem. And -.12 we are
looking at this particular problem now.
If you wnat to find out what is causing your error 8, I will need
the errorlog entry and if you can't provide that then at least
enter the port status register contents, the msgid and the userdef
registers. These register will allow me to see what is causing the
fault.... Error 8 means absolutely nothing to me by itself
Maureen
|