[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

1765.0. "No firmware loaded in new DECagent?" by AKRON1::SMITH (Sic Semper Potatum Reclinus) Tue Dec 06 1994 12:29

    I installed a DECagent module into a DEChub 90. When it powered up I
    observed that the DC OK, Self-test OK and Network OK lights were on
    solid and the Network Activity light was flashing at 1 second
    intervals.  Having never dealt with a DECagent before I assumed that I
    should be able to connect a terminal and get the documented response
    and go on from there.  In this case however, I got NO response.
    
    After eliminating most of the possible problems, I decided to see if
    the DECagent was presenting anything to the LAN.  Much to my surprise I
    found that I would multicast a downline load request for its firmware
    image (DENMA021.SYS).  It would do this after the self-test completed
    and only ONE TIME (????).  So, just for kicks, I placed the
    DENMA021.SYS file in MOM$LOAD on my vax, jammed the DECagent in the hub
    and the vax loaded it with no problem.  In fact,  after the load the
    lights looked like they were supposed to look - DC OK, Self-test OK on
    solid and Network OK and Network Activity alternating at a 1 second
    interval.  Then when I connected a termnal to it,  the menu displayed.
    However,  this too is odd since the book says that it should ask for a
    console password.
    
    
    This can't be normal.....
    
    If I were a customer (or an MCS engineer), I would've declared this
    module DOA!
    
    Anyone have a comment??
    
    
    Jeff Smith
    MCS Systems Support Engineer
    Cleveland Ohio
    DTN 431-2712
T.RTitleUserPersonal
Name
DateLines
1765.1Two strikes!ROGER::GAUDETBecause the Earth is 2/3 waterTue Dec 06 1994 13:0323
Jeff,

No, it is not normal.  We recently discovered that the folks in Augusta (Maine, where
the DECagent is manufactured) allowed an unknown number of DECagent's to pass through
their Final Quality Check process without verifying that the final firmware image
(V2.1.3) had loaded successfully.  This left the devices loaded with only an
intermediate loader image (whose sole purpose in life is to broadcast a request for
DENMA021.SYS).  Strike one.

As for the bogus documentation, we have also discovered that Augusta is shipping the
V1.1 User's Guide with the latest DECagents.  This is *very* misleading as the setup
menu has completely changed in V2.x of the firmware.  Strike two.

You can copy an on-line version of the V2.x Installation and Configuration Guide from
the following:

	TNPUBS::PUBLIC$DISK:[PUBLIC.ONEHUB]DECAGENT90_INS_V2_0_EK_DENMA_IN.PS;1

The order number is EK-DENMA-IN.A01.

And yes, we have notified them of the problems.  They will hopefully be fixed soon.

...Roger...
1765.2Please inform us if other DOA's foundNETCAD::WALTERTue Dec 06 1994 13:5616
    I'll add one point to Roger's reply: We already have found one of the
    unloaded DECagents that was requesting a load of DENMA020.SYS, not
    DENMA021.SYS. So if copying the most recent firmware into MOM$LOAD and
    naming it DENMA021.SYS doesn't work, then try naming it DENMA020.SYS.
    If that still doesn't work, you can always perform the two step load as
    a brute force method of loading the agent.
    
    I think Augusta is still trying to determine how many of the DECagents
    were affected. If you find such a "DOA" DECagent, please note down the
    module's MAC address from the front panel and the serial number from the
    back panel (it begins with the letters "AS") and send that data to me,
    along with a brief description of the circumstances. I will forward the
    information to Augusta.
    
    Dave
    
1765.3Here's the poop!AKRON1::SMITHSic Semper Potatum ReclinusTue Dec 06 1994 14:0718
    WOW!!!  That was fast!!!!
    
    re: .1   
    Thanks for the doc pointer.....BTW, how many strikes do we get
    these days??
    
    re: .2  
    The DECagent in question is S/N AS44607620 MAC addr 08-00-2B-94-5d-87
    
    
    This module was a replacement for a DECagent I received last week that
    wouldn't even pass self-test....unfortunately, I don't have any more
    info....  Now I wonder if it may have been shipped without ANY code in
    it.....
    
    I guess life -IS- like a box of chocolates!!
    
    -jas
1765.4Found 1 like this last week.TROFS::WEBSTERNIS, London, CanadaFri Dec 30 1994 15:3015
	One of the local MCS people came to me just last week with this load
problem. Agent was requesting DENMA020.SYS. He gave the module to me to see
if I could see what was wrong. 

	Not being able to update with DECndu, the module was sent back thru
the repair cycle to be fixed.

	Unfortunately, I did not not keep the MAC address or serial # of the
unit, and just found this note today.

	Contact me directly if you would like the serivce call #, as it may
be trackable thru that.

	-Larry
	 NPC, London, Ontario