| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE | 
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 | 
| Moderator: | NETCAD::COLELLA DT | 
| 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 | 
  Hi!
  We tried DETMM F/W update from 1.0G to 2.0.0, and trouble occured.
  DETMM restart fail after NEW F/W V2.0.0 down load complete .
  BAD DETMM display several pattern led lit and stay "power ok",
  "network ok" ,and "1" LEDs lit on when power up.   
  Other Modules update are normal complete.(dmhub410,defba152,def6x311)
  I guess,
	If DETMM port communications active (W/Ss communicate through DETMM),
	DETMM update incomplete.
	
	Because We success update DETMM that have no connection. 
  I want know,
	Is ther any requirement for DETMM V2.0.0 update ?
 
	DEChub900 mam version : V4.1.0
  	DECrepeater900 version: HW=v2,RO=v1,SW=v1.0G
	HUB module config		
		slot1 :  DECbridge900
		    2 :  DECconcent900
		    3 :  DECrepeater900
		    4 :  DECserver900
		5-8   :  blank
		        	VS4000 M90A  <--- load host   
				         +	
		HUBswitch900#0		 + (10baseT)
			(DEFBA DEF6M  DETMM)
			  \     \
			  \     \ (FDDI DAS)
		 \\\\\\ GIGASWITCH \\\ 	
		 \	             \
                 \                   \ 
HUBswitch900#1	 \	             \
 	(DEFBA DEF6M  DETMM)         \ (FDDI DAS RING)
	   \                         \
	     \                       \
HUBswitch900#2 \	fail	     \
	(DEFBA DEF6M  DETMM)         \
	   \                         \
             \                       \
HUBswitch900#3 \	fail	     \
	(DEFBA DEF6M  DETMM)         \
           \                         \
           \\\\\\\\\\\\\\\\\\\\\\\\\\\
    
    Thanks for any answer.
    Mune
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 2840.1 | Second failure of exact same type | ROMEOS::HARRIS_MA | Sales Executive II | Mon Oct 09 1995 19:44 | 6 | 
|     THIS IS EXACTLY WHAT HAPPENED TO ME! PERHAPS SOMEONE COULD LOOK AT THE
    ISSUE BACK IN LKG?
    
    My DR900TM is still very dead, exactly as described in previous note.
    
    Mark
 | |||||
| 2840.2 | Engineering is checking | NETCAD::ROUNDS | Tue Oct 10 1995 10:08 | 6 | |
|     We are currently doing upgrades on DETMM to see if there is an upgrade
    problem.
    
    
    
      
 | |||||
| 2840.3 | at least 15minutes before unpower. | ROMEOS::HARRIS_MA | Sales Executive II | Tue Oct 10 1995 14:04 | 6 | 
|     Thanks for looking into it. I didn't touch the module for more than
    15mins after the upgrade started. I assumed it wouyld come back on-line
    by itself and then after 15min. I pulled the module and then
    re-installed it to try and reset.
    No luck,
    M
 | |||||
| 2840.4 | re: CONFIGURATION | TKTVFS::OHTSUKA_MU | Wed Oct 11 1995 01:32 | 94 | |
| 
Hi! 
Thanks for your reply.
Today We tried 3 DETMM update again and one DETMM failed .
[ Fail log]
	
KekMC1> download load /force=pcommon 130.87.143.5 detmm200.bin
(c) Digital Equipment Corporation. 1993. All Rights Reserved.
DECNDU: (TFTP) Target address = 130.87.143.5
[PCOMMON] Getting sysDescr
   DECrepeater 900TM 32 Port TP Ethernet Rptr SNMP, HW=v2,RO=v1,SW=v1.0G
[PCOMMON] Setting server IP address (pcomLoadIpHostAddr).
[PCOMMON] Getting Server IP Address
   130.87.1.17
[PCOMMON] Setting filename (pcomLoadFilename).
[PCOMMON] Get filename.
   DETMM200.BIN
[PCOMMON] Setting AdminStatus/trigger (pcomLoadAdminStatus).
[PCOMMON] TFTP serve.
DECNDU: (TFTP) Blocks sent = 903
DECNDU: (TFTP) Transfer Complete.
[PCOMMON] TFTP server completed.
[PCOMMON] Polling for sysDescr
[PCOMMON] Getting sysDescr
DECNDU: ERROR STATUS = No response from device.
Fail DETMM display lit on LEDs.
	DC ok,network ok
	1,2,3,6,7,8
	a,b,c,d                   total 12 leds.
And then RE-powered, DETMM display seviral pattern led and stop
below status
	DC ok,network ok
	1                         total 3 leds.
	
hardware description
	pn  DETMM-M
	rev C01
	sn  AS40205740
	mac 08-00-2b-a3-b2-59
 configuration
	LoadHost is VS4000m60 VAX system . 
	We use ndu+ (download command) and config summary is below.
	A Gigaswitch have 14 DAS ring for DECnis600s and 1 DAS ring
	for a hubswitch.
	Each DECnis600 have another DAS ring for HUBswitchs include
	target DETMMs for F/W v-up.
	One DECswitch have a VS4000 loadhost through a DECrepeater900.
 
	Down load path is
	VS4000 > DETMM > DEFBA > gigaswitch > DECnis600 
		> DEFBA on target hub> target DETMM
                  das ring
                  V
		G ----DECnis600 ---HUB#1---HUB#2---HUB#x-+
		I ----+       +                          +  <- das ring 
                G             +--------------------------+       for hub
           +--- A         |              |
       hub +--- s
       V        w         |              |
   VS4000       i    14             14 
   load host	c     DECnis600s      HUB rings 
                h
Regards,
Mune
 | |||||