[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

3031.0. "900mx dump" by NETRIX::"[email protected]" (steven Freke) Tue Dec 05 1995 12:36

Hello there,
	I have a customer, who has two 900mc bridges that are crashing at 
rather in convenient times. Below are two dumps, one from each.
If anybody can decipher them, we would be greatful.

Entry #		= 2
Entry Status	= 0 [0=valid, 1=write_error, 2=invalid 3=empty 4=crc_error]
Entry Id 	= 10
Firmware Rev	= 1.4
Reset Count 	= 15
Timestamp	= 	0	f  91b4
Write Count	= 6
FRU Mask	= 0
Test ID		= DEAD
Error Data	= SR=2004  PC=00000242  Error Code=00002010  ProcCsr=776d
Registers	= 00=00000000 D1=0000007F D2=00000072 D3=00000018
		  D4=0004a800 D5=00000000 D6=00000000 D7=0000FFFF
		  A0=00000000 A1=0004a798 A2=0440f82A A3=00061880
		  A4=030030D8 A5=03020000 A6=0002c640 A7=0004A890

The dump for the second MX is as follows:

Entry #		= 1
Entry Status	= 0
Entry Id	= 10
Firmware Rev	= 1.4
Reset Count	= 15
Timestamp	=    0   F 91B9
Write Count	= 6
FRU Mask	= 0
Test Id 	= DEAD
Error Data	= SR=2000  PC=00074966  Error Code=0000200c  ProcCSR=776D
Registers	= D0=00000000 D1=0000007F D2=00000078 D3=00000018
		= D4=0004A8d0 D5=00000000 D6=00000000 D7=0000FFFF
		= A0=00000000 A1=0004A798 A2=0440F82A A3=00061880
		= A4=030020D8 A5=03020000 A6=0002C610 A7=0004A888

My fingers are glad that bit is over. If anyone has any ideas then please 
let me know.

Regards
	Steven Freke
	LAN Team
	UK CSC
[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
3031.1Upgrade your bridges to rev 1.5.2NETCAD::BATTERSBYTue Dec 05 1995 12:417
    My strong suggestion after looking at the Firmware rev in the
    error log message is to get those units upgraded to the most
    current rev (FW=1.5.2). There have been bugs fixed that existed
    in the 1.4 rev of firmware.
    So do yourself a favor and upgrade those units asap.
    
    Bob
3031.2One small problemNETRIX::"[email protected]"Steven FrekeWed Dec 06 1995 03:4814
Bob
	Yeah that is what I suggested to the customer. But he can't upgrade 
hub or his modules, until he upgrades to the latest version of hubwatch. 
At the moment is is running hubwatch v4 for vms. And the next release is not
out yet. So he is stuck where he is. 

I don't really want to see him running the modules and hub etc, on different
revisions. And if we id the modules would be unmanageable. Therefore setting
up the virtual lans would be a little difficult.

Any further input?

	Steven
[Posted by WWW Notes gateway]
3031.3Another way out possibly....NETCAD::BATTERSBYWed Dec 06 1995 10:2212
    Steven, your base note didn't make mention of the rev of HUBwatch
    being used (on the VMS platform), So my context was limited to 
    getting the bridges upgraded. Yes there would probably be management
    incompatibilities.
    Knowing now what your customer limitation is, I have another
    suggestion. There is I think still available an interim image of
    DEFBA code (1.4.2), that fixes some of the bugs in the 1.4.0 image
    that might be causing your customers crashes. To get this image
    I suggest contacting Bill Wade (NPSS::WADE), and he should be able
    to provide you a pointer for the binary image.
    
    Bob
3031.4keep versions compatibleNETCAD::CURRIERWed Dec 06 1995 11:335
    Your customer can not run the modules & hub against a hubwatch that is
    not the correct version.  You are right not to advise this.  The FDDI
    LAN interconnections on the backplane would become horribly corrupted.