[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

1622.0. "Problem Upgrading DENMA V1.1 to V2.1.3" by SVCVAX::GAMBARDELLA (Gamby Gumba) Thu Oct 27 1994 00:37

I am having trouble upgrading a DENMA from v1.1 of the firmware to v2.1.3 
using NDUplus v1.0e.  I read the DECagent v2.1 release notes and it mentions 
using MOP rather than TFTP to perform the upgrade.  It also says that MOP
is used as the update protocol if the DECagents 90's MAC address is
specified as the target address to DECndu Plus.  I am typing the following 
command and getting back this error message:

$ download load/force=decagent 08-00-2b-3d-12-0a denma021.sys/pass="public"

(c) Digital Equipment Corporation. 1993. All Rights Reserved.
%NDU-E-READ_DEVICE, error during read device
%NDU-E-NORESP_ERR, no response from target
%NONAME-E-NOMSG, Message number 00000002

I have also tried the same command I used to upgrade the v2.0 DENMAs 
at this site to v2.1.3 and get the following error:

$ download load/force=decagent 149.132.98.220   denma021.sys/pass="public"

(c) Digital Equipment Corporation. 1993. All Rights Reserved.

DECNDU: (TFTP) Target address = 149.132.98.220
[DECAGENT] Getting sysDescr
   DEChub 90 8 slots, DECagent 90 HW=D01 ROM=BL05.00 SW=V1.1y
[DECAGENT] Setting server IP address (da90LoadIpHostAddr).
[DECAGENT] Getting Server IP Address
   0
[DECAGENT] Setting filename (da90LoadFilename).
[DECAGENT] Get filename.
   0
[DECAGENT] Setting AdminStatus/trigger (da90LoadAdminStatus).
[DECAGENT] TFTP serve.
 
DECNDU: (TFTP) TIMEOUT on port.
[DECAGENT] TFTP server completed.
[DECAGENT] Polling for sysDescr   
[DECAGENT] Getting sysDescr
DEChub 90 8 slots, DECagent 90 HW=D01 ROM=BL05.00 SW=V1.1


Can anyone help me out with this - I have several DENMAs at v1.1 and I need 
get them up to v2.1.3 to use them under HUBwatch 3.0

Thanks,

Mike Gambardella
RCH MCS
T.RTitleUserPersonal
Name
DateLines
1622.1No qualifiers necessary for MOP loadROGER::GAUDETBecause the Earth is 2/3 waterThu Oct 27 1994 14:2518
A couple of things.

First, you do not need the /FORCE and /PASS qualifiers when doing a MOP load. 
These are only necessary when updating using TFTP.  I am not sure what DECndu
does if you specify these qualifiers when doing a MOP load, but based on the
results you posted I suspect that they don't work well together.  Use the
following command line for your V1.1 DECagents:

$ download load <Ethernet_Address> denma021.sys

Second, what you saw when trying the TFTP load is pretty much what I would
expect.  The SNMP set and get requests that DECndu generates during a TFTP load
will all fail.  However, I think DECndu gets confused and "claims" that the load
is in progress (even though it really isn't).

Try the above command and see if that fixes your problem.

...Roger...
1622.2Had to Replace DENMASVCVAX::GAMBARDELLAGamby GumbaWed Nov 16 1994 17:1814
RE: .1

Thanks for your suggestion, but I never got a chance to try it.  The customer
played around with it after I left and somehow caused that DENMA to fail its 
self test.  I replaced that DENMA with one from stock and the replacement 
one came in at V2.1.3.  Now he wants all his DENMAs replaced, because of this
the project is on hold until we straighten out this DENMA issue.

If/when I get the go ahead to try again, I'll let you know if your suggestion
works. 


Thanks...

1622.3DENMA upgrade problem any version.GIDDAY::DANIELThu Mar 30 1995 05:2641
	I have problems upgrading Decagent 90s either through TFTP or MOP from
	any version. Customer tried V1.1 & V2.0 & H/W versions B01, D01 & D02.

	1. TFTP upgrade expects the file DENMA.NDU_SCRIPT which I could not find
	   anywhere including ftp.digital.com, CDROM & TIMA. Can you please post
	   a copy of that file here.

	2. "download sho dev 08-00-2b-94-c7-b9" gives the following error.

		(c) Digital Equipment Corporation. 1993. All Rights Reserved.
		%NDU-E-READ_DEVICE, error during read device
		%NDU-E-NORESP_ERR, no response from target
		%NONAME-E-NOMSG, Message number 00000002

	   "download load 08-00-2b-94-c7-b9 mom$load:denma021.sys"
	   gives the same message.

		(c) Digital Equipment Corporation. 1993. All Rights Reserved.
		%NDU-E-READ_DEVICE, error during read device
		%NDU-E-NORESP_ERR, no response from target
		%NONAME-E-NOMSG, Message number 00000002

	   I have tried this both in the Dechub900 & standalone.

	   The only thing that works is

	   "download sho dev 16.153.32.215"

		(c) Digital Equipment Corporation. 1993. All Rights Reserved.
		[SYSDESCR] Getting Device INFO (sysDescr)
		DEChub 90 8 slots, DECagent 90 HW=D01 ROM=BL05.01 SW=V2.1.3

	   "download sho ver"

		(c) Digital Equipment Corporation. 1993. All Rights Reserved.
		DECndu (Network Device Update) Utility PLUS V1.0e

	Thanks in advance.
	Daniel.
	CSC, Sydney.

1622.4Once again, it's all documentedROGER::GAUDETBecause the Earth is 2/3 waterThu Mar 30 1995 11:3918
DENMA.NDU_SCRIPT is provided in the distribution saveset (DENMA021.A for OpenVMS
and denma210.tar for ULTRIX).  If your customer received an official
distribution kit through SSB for the DECagent 90 firmware, then they have this
file.  The documentation is quite clear on this.  Read the release notes.

Everything you need is online at NETCAD::PROJ$722:[ONEHUB.RELEASE.DENMA.V2.1].

As for the DOWNLOAD SHOW command, using a MAC address causes NDU to issue an
RBMS SHOW DEVICE command which the DECagent 90 does not support.  You can,
however, cause a MOP load of a DECagent 90 by using the /NOMANAGEMENT qualifier
with the MAC address:

	$ DOWNLOAD LOAD /NOMANAGEMENT <MAC_address> <file_name>

This will only work if your DECagent 90 is running at least V1.1 firmware.  See
the release notes for details on how to load a DECagent 90 running V1.0.

...Roger...
1622.5One of those days, I suppose!GIDDAY::DANIELThu Mar 30 1995 15:0113
Roger,

Thank you for the prompt reply.

My profuse aplogies for my oversight. I did unpack the saveset & got the 
denma021.sys & the rest of the files. I even read the release notes!

I suppose it is one of those days!


God bless.

Daniel.
1622.6Save some time ...ROGER::GAUDETBecause the Earth is 2/3 waterThu Mar 30 1995 17:0011
No problem Daniel, we all have those kind of days.

You might want to save yourself a step (merging the DENMA.NDU_SCRIPT file) by
just copying the following file to your SYS$SYSTEM directory:

	NETCAD::PROJ$722:[ONEHUB.RELEASE.FIRMWARE.V1_1.VMS]NDU$SDDF.STP

This file already has the DENMA.NDU_SCRIPT merged into it and a couple of minor
identification fixes for some of the modules which NDU can load.

...Roger...