| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2039.1 | Wrong command line! | ROGER::GAUDET | Because the Earth is 2/3 water | Wed Feb 22 1995 11:17 | 8 |
| You want to use the /m (that's the 'module' switch) instead of /n (that's the
'nomanagement' switch which only applies to MOP/RBMS upgrades).
Try this command line instead:
decndup /u /f hubmanv2 /m 9 16.68.16.226 c:\firmware\dmhub310.bin
..Roger...
|
| 2039.2 | Hub 900 v3.0.0-v3.1.0?? | NEWOA::HARRISON | To be or not to be eligible? | Fri Feb 24 1995 07:50 | 10 |
| Hi,
Like .0 I need to upgrade my DEChub 900 to v3.1.0. I'm currently
running v.3.0.0. Should I still use the syntax...
a:\decndup /u /f HUBMANV2 /m 9 16.182.192.214 c:\firmware\dmhub310.bin
Is the target name for the upgrade still HUBMANV2 if I upgrade fromv3?
Thanks Al
|
| 2039.3 | YEP | CONSLT::BUZZELL | | Fri Feb 24 1995 09:13 | 6 |
|
YES. HUBMANV2 is a system descriptor and has nothing to do
with the fiemware level. You just specify the right file as you
have on the end of the string.
|
| 2039.4 | error downline loading | NEWOA::HARRISON | To be or not to be eligible? | Fri Feb 24 1995 09:33 | 19 |
| Ok tried it and failed with following error...
[CDI_BIND Error -DLL_OPEN failed - 000c]
DECnduplus: Beginning downline load
HUB Background:
My Hub is on an isolated LAN from the Easynet, however the the Hub and
associated modules have been allocated unique DEC IP addresses.
Customers will test WAN links out from our LAN when carrying out
Disaster Recovery tests. We have no name server or gateway on the LAN.
A PC running hubwatch for Windows v3.1 is the management platform. I
have created a DECndup diskette and modified the SDDF.STP file to point
to the PC IP address, I did specify the local nameserver and gateway on
easynet, I assume this info will be ignored for the purposes of
upgrading firmware on one local LAN??
Can you offer any help.
Thanks Al
|
| 2039.5 | NIC setup problem? | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Feb 24 1995 12:14 | 7 |
| RE: .4
That really looks like a network configuration problem (i.e. your PROTOCOL.INI
file is not setup properly for your NIC). Is the BIND error the very first
thing that comes up or are there any DECNDU messages prior to it?
...Roger...
|
| 2039.6 | It works! | NEWOA::HARRISON | To be or not to be eligible? | Mon Feb 27 1995 09:31 | 4 |
| Ok fixed it, I had to copy the Hubwatch for Windows v3.1 protocol.ini
onto the DECndup bootable diskette, everything has worked fine.
Thanks Al
|
| 2039.7 | | TOOK::PASQUALE | | Mon Feb 27 1995 12:57 | 4 |
| hmm.. don't recall seeing that in the readme document... ?
/ray
|
| 2039.8 | Just be glad I don't make the decisions! :-} | ROGER::GAUDET | Because the Earth is 2/3 water | Mon Feb 27 1995 14:58 | 19 |
| RE: .7
That's because it doesn't belong in the README file. Getting your PC's network
connection up and running is *NOT* the responsibility of the application (this
is also a hot button for me with respect to HUBwatch for Windows).
You pick up the DECndu Plus kit (or HUBwatch for Windows), install it and then
expect it will just work with your particular configuration. And when it
doesn't, you blame the application. WRONG!!! The mistake we in Engineering
have made is in trying to be nice and "assist" in getting your network
connnection up and running.
If I had my way, the following would appear right at the top of the README file
for DECndu Plus, HUBloader and HUBwatch:
THIS APPLICATION REQUIRES A WORKING NETWORK CONNECTION. SETUP, CONFIGURATION
AND VERIFICATION OF THE NETWORK CONNECTION ARE THE RESPONSIBILITY OF THE USER.
...Roger...
|
| 2039.9 | *** CONCUR !!!!!!!!!!!!!!!!! *** | NETCAD::WAGNERCOFFIL | | Tue Feb 28 1995 10:49 | 6 |
| >>THIS APPLICATION REQUIRES A WORKING NETWORK CONNECTION. SETUP, CONFIGURATION
>>AND VERIFICATION OF THE NETWORK CONNECTION ARE THE RESPONSIBILITY OF THE USER.
ROGER, THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Barb
|