[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

4197.0. "DS900 downline load ..." by BERFS4::NORD () Mon Feb 03 1997 13:21

    
    
    Hi you, (you know me, I'm the one who starts with: Good morning, good
    ...
    
    
    6 DEFBAs, all standalone, customer wants to upgrade from 1.5.2 to 1.6.1
    or better to 1.7.0.
    
    We have done it via telephone and it is running without any problem
    (test equipment!). The customer has done it the last weekend and there
    has been one problem:
    
    
    	He upgraded, but there was no response to the initial question of
    	the "loader": ... new firmware ..., ... new firmware .., ...,
    	the DEFBA/DExxx seems to be dead!
    
    Is there any help for that problem or do I have to escalate it?
    
    Many thanks in advance
    
    Wolfgang Nord
    MCS@BEO@GERMANY
    
    
T.RTitleUserPersonal
Name
DateLines
4197.1Need mode detail on customer's perception of "dead"...NETCAD::BATTERSBYMon Feb 03 1997 15:1520
    Can you confirm with the customer what the state (present condition)
    of the "dead DEFBA" is? Does it exhibit the led behavior of a DEFBA
    trying to do a bootp (I'm presuming you know what to look for and how
    to describe this to the customer)? 
    IE: Can you get more detail from the customer what they perceive
    they mean by a "dead DEFBA"?
    The customer may have either have tried loading it with a corrupt
    binary image, or didn't wait long enough before possibly power cycling 
    it (as we have seen other customers do).
    However I suppose that if they have upgraded the other standalone
    units with good results, then the binary image is not the source of
    the problem.
    
    >>He upgraded, but there was no response to the initial question of
    >>the "loader": ... new firmware ..., ... new firmware .., ...,
    
    I'm not sure I understand what is meant by this statement. Can you
    elaborate on this?
    
    Bob