[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

3080.0. "900TM upgrade problems." by CGOS01::DMARLOWE (Have you been HUBbed lately?) Mon Dec 18 1995 12:12

    I just upgraded or tried to upgrade 7 900TM's in a customer's hub.  All
    units were at firmware V1.0G but varied in terms of ROM and hardware.
    
    1 - HW=V1  RO=V1    SW=V1.0G
    2 - HW=V2  RO=V1    SW=V1.0G
    3 - HW=V3  RO=V1.04 SW=V1.1
    4 - HW=V2  RO=V1.04 SW=V1.1 spare unit added to hub for additional
                                 ports
    
    Units 1 & 2 when direct loading, HUBLOADER would indicate the units
    were loaded in 3 seconds flat.  The 900TM's would reboot immediately
    but would still come up at V1.0G.
    
    Unit 3 upgraded smoothly with no problems.
    
    Unit 4 when completed self tests would cause the MAM to fail, (showed
    failed at PC message) and then reboot.  This would continue as long as
    unit 4 remained in the hub.  Upgraded unit 4 in a ONEHUB and then put
    it back into the hub and all was fine.
    
    Any comments on units 1 & 2 and on unit 4?
    
    dave

T.R	Title	User	Personal Name	Date	Lines
3080.1		NETCAD::MILLBRANDT	answer mam	`Mon Dec 18 1995 13:11`	6
	Just for grins, could you dump the MAM error log and see what the crash PC was, and what version of MAM code is running? Line card states, whether good or bad, shouldn't zap the MAM's self test! Dotsie
3080.2	A real MAM killer.	CGOS01::DMARLOWE	Have you been HUBbed lately?	`Mon Dec 18 1995 14:55`	10
	The mam had just been upgraded to V4.1 from V3.1. and then we were starting in on the 7 900TM's. The MAM was up and running fine and then when unit 4 was placed in slot 3 and completed its self tests, the MAM failed. As long as the 900TM remained in the chasis, everytime the MAM came up, it displayed slots 1 and 2 OK. When it went to display slot 3 it reset. Apparently it was a RESET TO FACTORY as I had to put the IP address back in to the MAM. dave
3080.3	it was a suicide	NETCAD::MILLBRANDT	answer mam	`Mon Dec 18 1995 17:06`	10
	Aha. You've given a good clue - something about displaying the module type and status goes belly up when the module isn't healthy enough to tell you. As to the factory reset, the MAM deliberatly does that if it crashes several times in a row in a short period of time. It figures it's something about the info saved in non-volatile RAM that is causing the problem, so it wipes that out. Dotsie
3080.4	ASSUMPTIONS - the mother of all... resets.	CGOS01::DMARLOWE	Have you been HUBbed lately?	`Tue Dec 19 1995 01:51`	12
	Yea, I know the MAM does a RESET TO FACTORY if a module resets a certain number of times in a given time period. Unfortunately I didn't look or count for that matter as it was a 900TM of mine and since it has been used before without any problems I ASSUMED there would be no problems other than old firmware. Any comments on the first 2 that would not accept a TFTP load? dave
3080.5	When all else fails, wait!	CGOS01::DMARLOWE	Have you been HUBbed lately?	`Tue Jan 02 1996 13:54`	5
	The customer did upgrades on 2 other hubs over the holidays. The 2 900TM's that would not accept a load, did. Must be the pull of the moon or something like that. Go figure. dave