| 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 |
I am working with a customer that is trying to upgrade their DH900
firmware from V2.2.1 to V3.1.0. They are using DECndu Plus v1.0 and it
seems to hang after starting the tftp server, customer has left it in
this state for as long as 3 1/2 hours. He can ping the DH900 using it's
inband ip address, and says that the DECndu software is able to
determine which version of the firmware is currently on the DH900.
Customer believes that I/O is occuring during the "hang".
I have incuded the commands used as well as the display on the screen
up to the point of the hang, any suggestions would be appreciated.
We have tried the string with and without the /password, there was no
response without the password.
Gene
$ download load /force=hubmanv2 /module=9 /password="kcmon"
/134.193.10.199/ mom$load:dmhub310.bin
(c) Digital Equipment Corporation. 1993. All Rights Reserved.
%LIB-E-KEYNOTFOU, key not found in tree
DECNDU: (TFTP) Target address = 134.193.10.199
[HUBMANV2] Getting sysDescr
Hub900MultiSwitch,DEChub 900 MultiSwitch,HW=F,RO=V1.1.6,SW=V2.2.1
[HUBMANV2] Setting (ChasLoadEntryStatus) to CreateRequest (2)
[HUBMANV2] Set load host IP address (ChasLoadIpHostAddr)
0.0.0.0
[HUBMANV2] Setting load filename
MOM$LOAD:DMHUB310.BIN speed, speed unchanged.
[HUBMANV2] Setting (ChasLoadEntryStatus) Valid (1)
[HUBMANV2] Setting (ChasLoadAdminStatus) Start-read (2)
[HUBMANV2] STARTING TFTP SERVER
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1513.1 | Need more information | ROGER::GAUDET | Because the Earth is 2/3 water | Mon Oct 03 1994 15:37 | 12 |
* What version of VMS?
* Is the UCX TFTP server disabled?
* Does the command line you specified really have forward slashes ("/")
encompassing the target IP address? (e.g. /134.193.10.199/) If so, that's an
improper syntax for the command line.
* It looks like UCX is not setup properly since the load host IP address is
being set to 0.0.0.0. Check for the logical UCX$INET_HOSTADDR at the DCL prompt.
...Roger...
| |||||
| 1513.2 | additional information | CSC32::MAULUCCI | Mon Oct 10 1994 10:39 | 26 | |
Thanks for the reply Roger (-.1)
The customer is running 5.5-2 OVMS, they are using "Multinet" rather
than "UCX". We have defaulted the dh900 and re-entered the IP address.
The DECndu utility can communicate with the hub as it displays the hubs
current firmware version as shown below:
$ download load /force=hubmanv2 /module=9 /password="kcmon"
134.193.10.199
mom$load:dmhub310.bin
(c) Digital Equipment Corporation. 1993. All Rights Reserved.
%LIB-E-KEYNOTFOU, key not found in tree
DECNDU: (TFTP) Target address = 134.193.10.199
[HUBMANV2] Getting sysDescr
Hub900MultiSwitch,DEChub 900 MultiSwitch,HW=F,RO=V1.1.6,SW=V2.2.1
[HUBMANV2] Setting (ChasLoadEntryStatus) to CreateRequest (2)
[HUBMANV2] Set load host IP address (ChasLoadIpHostAddr)
0.0.0.0
[HUBMANV2] Setting load filename
MOM$LOAD:DMHUB310.BIN speed, speed unchanged.
[HUBMANV2] Setting (ChasLoadEntryStatus) Valid (1)
[HUBMANV2] Setting (ChasLoadAdminStatus) Start-read (2)
[HUBMANV2] STARTING TFTP SERVER
| |||||
| 1513.3 | You need the "other" version of NDU | ROGER::GAUDET | Because the Earth is 2/3 water | Mon Oct 10 1994 14:29 | 8 |
Your customer needs the version of DECndu Plus that was built for OpenVMS VAX V5.5 and later. According to the developer, the version from the SSB was never tested to run with TGV Multinet. He says the above version should do so. You can pick up this version on the network at NETCAD::PROJ$706:[NDU.V3.RELEASE.VMS.POST_VMS_5_5]NDUPLUS010.A ...Roger... | |||||