[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

1989.0. "MAM V3.0 to V3.1 upgrade problems!" by GLDOA::BREIMAYER () Thu Feb 09 1995 14:47

    Hi,
    
    	I have a customer who is implementing large numbers of Multi-switch
    900's and are using HUbwatch for Windows 3.1 and NDUPLUS 1.0.  When
    upgrading the hubs using NDUPLUS and the commands for HUBMANV2 to slot
    9 of the hub, this works fine for 2.1 MAM to 3.1 MAM.  When the
    customer try's to upgrade from V3.0 MAM to V3.1 MAM this command fails
    with "wrong version error".  The customer has tried using HUBMANV3 in
    their command with same failure and has tried the command for
    standalone IP device with same failure (they tried standalone IP
    commands for V2.1 MAM to V3.1 MAM and this worked so they know the commands
    are OK.  Currently they have three backplanes they are ready to ship
    back as bad unless there is some way to upgrade form V3.0 MAM.  Any
    suggestions or ideas?  If you have upgraded from V3.0 to 3.1
    successfully under NDUPLUS 1.0 for DOS please include the commands you
    used which I will relay to the customer.  Thanks in advance.
    
    Ted Breimayer
T.RTitleUserPersonal
Name
DateLines
1989.1Works OK for meROGER::GAUDETBecause the Earth is 2/3 waterThu Feb 09 1995 16:4544
Ted,

I must admit that I've never seen that error message from DECndu Plus.  I just
tried this on one of our hubs and it worked just fine.  What version of DOS is
the customer running when attempting the upgrade?

Here's the command log from my successful attempt:

A:\> decndup /V

(c) Digital Equipment Corporation. 1993. All Rights Reserved.
DECndu Plus (Network Device Upgrade) Utility V1.0 for DOS

A:\> decndup /s 16.21.2.83

(c) Digital Equipment Corporation. 1993. All Rights Reserved.
[SYSDESCR] Getting Device INFO (sysDescr)
   Hub900MultiSwitch,DEChub 900 MultiSwitch,HW=F,RO=V1.1.6,SW=V3.0.0
DECnduPlus: SUCCESS

A:\> decndup /u /f hubmanv2 /m 9 16.21.2.83 c:\firmware\dmhub310.bin

[HUBMANV2] Getting sysDescr
   Hub900MultiSwitch,DEChub 900 MultiSwitch,HW=F,RO=V1.1.6,SW=V3.0.0
[HUBMANV2] Setting (ChasLoadEntryStatus) to CreateRequest (2)
[HUBMANV2] Set load host IP address  (ChasLoadIpHostAddr)
  16.21.16.121
[HUBMANV2] Setting load filename
  c:\firmware\dmhub310.bin
[HUBMANV2] Setting ChasLoadEntryStatus) Valid (1)
[HUBMANV2] Setting (ChasLoadAdminStatus) Start-read (2)
[HUBMANV2] STARTING TFTP SERVER
BLOCKNo = 959   BYTES = 490496
[HUBMANV2] TFTP DOWNLOAD COMPLETED
DECnduPlus: SUCCESS

..... after waiting a few minutes for the new code to be written to FLASH .....

A:\> decndup /s 16.21.2.83

(c) Digital Equipment Corporation. 1993. All Rights Reserved.
[SYSDESCR] Getting Device INFO (sysDescr)
   Hub900MultiSwitch,DEChub 900 MultiSwitch,HW=F,RO=V1.1.6,SW=V3.1.0
DECnduPlus: SUCCESS
1989.2tested now in my favorite PC and HUBPRSSOS::PEYRACHEJean-Yves Peyrache Country Support Group FranceThu Feb 09 1995 17:028
 C>DECNDUP /u /f hubmanv2 /m 9 x.x.x.x c:\firmware\dmhub310.bin

  x.x.x.x equal address ip of your hub900

  hope that's help you

  jean-yves