T.R | Title | User | Personal Name | Date | Lines |
---|
1541.1 | No solutions, but some questions.... | PROXY::JEAN | MAUREEN JEAN | Wed Dec 28 1994 14:44 | 13 |
|
Can you get me the revision of the hardware?
Unfortunately you will have to look at the module to
do this. Also, you said that you changed DEMFA's.
Does this mean you replaced both modules out or swapped
DEMFA's in the two systems? Is this a new configuration?
If not, has anything recently changed??
Thanks,
Maureen
|
1541.2 | See note 395 in school::gigaswitch | ANGLIN::MILLER | | Wed Dec 28 1994 21:23 | 7 |
| I have cross posted this note in the Gigaswitch conference as it
appears to be the problem. Please see note 395 there.
Regards,
Dale
|
1541.3 | Same errors | ANGLIN::HUGHESD | | Tue Mar 28 1995 12:30 | 153 |
| I'm receiving the same errors in my system with the only difference being tha
fact that I don't have a Gigaswitch on this network.
I have 2 Alpha 7610's DSSI clustered together each with 2 DEMFA FDDI
controllers (the 2nd one's circuit is turned off because they still run Decnet
phase IV). I don't know the module revision but, I want to say it's F something.
I will check it the next time I'm on site.
The DEMFA logs receive format errors intermitantly and I swapped the 2 DEMFA's
with no change on symptoms.
Recently I discovered that I could reproduce the errors by logging into a
decserver via NCP with the following command.
NCP> conn node xxxxxx via mfa-0 physical address 08-00-2b-xx-xx-xx
After a short period of time on the Decserver (making port changes), I (and all
the lat users) would get bumped off back to the NCP prompt and the DEMFA would
log the errors.
Here is a example of the errorlog. Any help would be greatly apreciated.
Thanks,
Dave
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
****************************** ENTRY 4838. *******************************
ERROR SEQUENCE 5342. LOGGED ON: CPU_TYPE 00000002
DATE/TIME 24-MAR-1995 14:03:22.95 SYS_TYPE 00000003
SYSTEM UPTIME: 3 DAYS 02:13:58
SCS NODE: ESOH01 OpenVMS AXP V6.1
HW_MODEL: 00000401 Hardware Model = 1025.
DEVICE ATTENTION DEC 7000 Model 610
DEMFA SUB-SYSTEM, ESOH01$FXA0:
ERROR TYPE CODE #8., ERROR SUBTYPE CODE #35.
XDEV REG 05200823
DEVICE TYPE = 0823(X)
FIRMWARE REV = 20(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 20
ERROR REASON 03
TIME STAMP 026E0000D800
15. HRS, 21. MINS, 36. SECS
WRITE COUNT 0005
MSGID 00000203
USRDEF0 01200000
USRDEF1 00000008
USRDEF2 00000001
PARICR 00000000
PMCCSR0 22002003
REM ENABLE
REM FREEZE
RMC DISCARD XMT-WRITE TRANSAC.
MEMORY MANAGEMENT ENABLE
PMCCSR1 025CFF00
PMCCSR2 01200000
MASK AM DEST PKT DISC INTRRPT
MASK HOST DEST PKT DISC INTRPT
PMCCSR3 00000000
ESP ERROR REG 00000008
RECEIVE FORMAT ERROR
XBE 0000008A
XFADR 01848520
XFAER 7800FFFF
XPUD REG 80000018
SELF-TEST COMPLETE
NORMAL MODE
NO FRU FAILURE
GPCSR 00000400
CLEAR OWNERSHIP ENABLED
INTCSR1 00000000
V M S SYSTEM ERROR REPORT COMPILED 28-MAR-1995 09:33:45
PAGE 2.
INTCSR2 00000400
AMIR 00000001
ESP ERR REG BITS ARE SET
VBR 00200000
CAAR 0000000C
CACR 00000001
DFC 00000007
SFC 00000007
UCB$L_ERTCNT 00010004
4. RETRIES REMAINING
UCB$L_ERTMAX 00000000
0. RETRIES ALLOWABLE
UCB$L_CHAR 0C442000
NETWORK
AVAILABLE
ERROR LOGGING
CAPABLE OF INPUT
CAPABLE OF OUTPUT
UCB$L_STS 00002010
ONLINE
UCB$L_ERRCNT 00000001
1. ERRORS THIS UNIT
V M S SYSTEM ERROR REPORT COMPILED 28-MAR-1995 09:33:45
PAGE 3.
******************************* ENTRY 4839. *******************************
ERROR SEQUENCE 5343. LOGGED ON: CPU_TYPE 00000002
DATE/TIME 24-MAR-1995 14:03:22.95 SYS_TYPE 00000003
SYSTEM UPTIME: 3 DAYS 02:13:58
SCS NODE: ESOH01 OpenVMS AXP V6.1
HW_MODEL: 00000401 Hardware Model = 1025.
DEVICE ATTENTION DEC 7000 Model 610
NI-SCS SUB-SYSTEM, ESOH01$PEA0:
FATAL ERROR DETECTED BY DATALINK
STATUS 0000045C
00001201
DATALINK UNIT 0001
DATALINK NAME 41584603
00000000
00000000
00000000
DATALINK NAME = FXA1:
REMOTE NODE 00000000
00000000
00000000
00000000
REMOTE ADDR 00000000
0000
LOCAL ADDR 000400AA
512D
ETHERNET ADDR = 0E-01-01-00-00-00
ERROR CNT 0001
1. ERROR OCCURRENCES THIS ENTRY
UCB$L_ERRCNT 00000002
2. ERRORS THIS UNIT
|
1541.4 | | NPSS::WADE | Network Systems Support | Tue Mar 28 1995 13:11 | 8 |
| You should escalate as an IPMT case against VMS. Mention that it is
the same problem as in IPMT case #23679. There is a new FXDRIVER
available for this problem.
Bill Wade
Network Product Support
|
1541.5 | | ANGLIN::HUGHESD | | Tue Mar 28 1995 14:39 | 7 |
| Bill,
Thanks for the quick reply. I have to escalate through the CSC so I
will start that process now.
Thanks,
Dave
|