Conference netcad::hub_mgnt

    
    
    Start TFTP Server FIRST before run Hubloader.
    It also happened to me.
    
    Jordi Manchon

    dave,
    
    there was a screw-up and hubwatch did NOT ship with firmware.  It was
    to be re-shipped with it when they figured it all out.  (This happened
    to me with RPS, etc., I bugged Bill Seaver about it and I believe that
    Mike Bouchard was in the process of fixing it.  However my guess is
    it's likely that if the customer is not on update service.....they may
    not get it.....but that's just a guess.
    
    ttfn,
    j
    

Can anyone offer any other reasons LOAD button wouldn't highlight.
Customer is telling me it wouldn't light and he had run TFTP_Server.

Dave

I've had the Load button go gray on me during a sequence
of loads that failed because I had the path name wrong.
Re-entering the "Load File" name turned it back on - I
suspect editing any of the Device Data fields would have
the same effect.

	Dotsie

    I have the same problem (sometimes) it seems that if I use the Hubwatch
    (Pathworks) IP stack, everyting is OK. If I use the MS stack or
    Chameleon Stack, it stays greyed out.
    
    	-Scott

    Not sure if this is the proper place but I'm trying to load new
    firmware from hubwatch and I'm getting this error. Not sure what to do
    so any helpful hints would be appreciated..
    
    Loading 16.122.0.75 with user specified data.
    Load Agent Name:  hurls99;   Agent Address:  16.122.0.75
    Slot Number: 2
    Community String: public
    [GIGAswitch] Setting TFTP Server IP Address.
    [ERROR] SNMP Set Request Timed Out
    [WARNING] Check Community String
    [ERROR] LOAD ATTEMPT FAILED
    
    John

    DO you have the "TFTP Server" box set to a valid TFTP server with the
    firmware images residing there? (About 1/3 of the way down, on the
    Right side of the dialog box, it will say "TFTP Server" and have a text
    box. That box needs a valid TFTP server IP address.)
    
    TFTP server set?
    
    Mark

    ...the problem is that you're not specifying the box address (lowest
    MAC address) as the community string, but using the default "public".
    
    MDL

    Mike,
    
    	Not sure what you mean by the box address. Below is a snapshot of
    the hubloader window
    
    		Firmware Version:
    	current			latest:
        2.0			2.20
    Load file /usr/kits/HUBwatch/fgl_22.rsx
    tftp server: 16.122.0.57
    Community Public
    
one the station & port Summary it says the station id is
    00-00-08-00-2b-a2-59-14 and over on the Mac Information it says 
    una 00-00-f8-00-00-00
    
    I tried that mac address but same error..

    
    If you look at the front of your GIGAswitch, you will see 
    2 parameters :
    
    	SA = <lowest MAC address>
    	DA = <highest MAC address>
    
    The GIGAswitch does not default its community name to �public� 
    as most DEChub products do, instead the lowest MAC address is used,
    you need to specify the value in SA = <> as the community
    name in HubLoader. If you don�t you won�t be able to 
    change any MIB variable in the GIGAswitch, what is needed
    for such things like, for example, telling the hub
    about a TFTP host and a file name to upgrade the firmware
    
    

           <<< SCHOOL::PUBLIC$DSK:[NOTES$LIBRARY]GIGASWITCH.NOTE;3 >>>
                                -< GIGAswitch >-
================================================================================
Note 463.1    Common problems encountered during firmware upgrades        1 of 6
NPSS::MDLYONS "Michael D. Lyons DTN 226-6943"        99 lines  21-APR-1995 15:17
                             -< A few typos fixed >-
--------------------------------------------------------------------------------
    Checklist for common problems encountered upgrading GIGAswitch/FDDI
    firmware:
    
    1) The read/write community string (password)
    
       SNMP sets are done during the load process, either explicitly or
    implicitly.  The "password" required for SNMP sets is the read/write
    community string.  On the GIGAswitch/FDDI system, the default
    read/write community string is the "box address", I.E. the lowest LAN
    address in the multiple address ROM installed on the clock module.
    
        If you are standing in front of the GIGAswitch/FDDI system, the
    easiest way to obtain the box address is to look at the front of the
    clock module, which is in slot 7.  The LAN address range should be on a
    label on the clock module.  The lowest address is the default
    read/write community string.
    
        If the label isn't there, you can get this information from OBM in
    the configuration part of the main menu.
    
        Note that the default read/write community string contains all
    lower case characters and no "-", ":", " " or other separators, I.E. it
    looks like 08002ba4c180
    
        Common errors:
    
    08-00-2b-a4-c1-80      "-" are not part of the default read/write
                           community string
    
    08002BA4C180           Upper case characters are not used in the
                           default read/write community string
    
    Note that to initiate the load using OpenVMS applications, you most
    likely need to encase the read/write community string in double quotes
    since otherwise it will probably be converted to uppercase for you. 
    I.E. you need to say "08002ba4c180"
    
    Also note that cutting and pasting the box address from OBM won't yield
    the correct results, since OBM displays it in upper case, separated by
    "-".
    
    2) IP
    
        See 265.1 for a list of the common problems associated with IP
    reachability.  The quick summary is to be sure you have an IP address
    assigned to the right ports, and a default gateway defined if you are
    communicating outside a subnet.
    
    3) Keyswitch position
    
        The GIGAswitch/FDDI system has four keyswitch positions.  The
    leftmost two key positions disallow SNMP Set requests.  The rightmost
    two key positions allow SNMP Set requests (Normal Access, or Easy
    Access (aka world access)).  Make certain that the keyswitch position
    allows SNMP Set requests.
    
    4) Load file names
    
        Various operating systems, and various server software have load
    file limitations.  Keep these in mind.  I.E. If you're using DOS, I
    think you're limited to 9 characters.  OpenVMS MOP is limited to 16
    characters.
    
        OpenVMS MOP supplies a default extension of .SYS if you don't
    supply it.
    
    5) load software
    
        Be certain that your load software does not conflict with existing
    network software.  I.E. NDUplus has its own tftp server built in.  It
    is possible that this may conflict with a pre-existing tftp service on
    the same system.
    
    6) Impatience
    
        Don't power cycle the GIGAswitch/FDDI system, or individual cards
    unnecessarily during the upgrade process.  Some cards take a long time
    to upgrade (AGL-2, PSC are the two slowest).  
    
        Starting with BL2.1, *all* the cards will reboot automatically when
    it is appropriate for the reboot to happen.  AGL-2 cards currently take
    about fifteen minutes to reboot!
 
        Be careful that you don't cause the GIGAswitch/FDDI system to
    reboot by upgrading the elected SCP card while the AGL-2 card is in the
    process of doing an upgrade!
       
    7) Retries
    
        On very busy networks, or networks with lots of errors, frame drops
    may cause the load attempt to fail - Just do a retry.
    
    8) Incompatible firmware
    
        Occasionally, there are dependencies in the various modules on
    other modules revision levels.  Please read the release notes for the
    proper order of upgrades.  Also check to see if management memory must
    be cleared.
                                                                      

    Well I'm getting closer but still not there..
    I now have the lowest mac address for the community, The key on the
    switch is turned to # 3. There is a ip address assigned to the port and
    this is what I'm getting now..
    
    Loading 16.122.0.75 with user specified data.
    Load Agent Name:  hurls99;   Agent Address:  16.122.0.75
    Slot Number: 2
    Community String: 08002ba25900
    [GIGAswitch] Setting TFTP Server IP Address.
    [GIGAswitch] Setting firmware image file name.
    [GIGAswitch] Triggering image file transfer.
    Community String: 08002ba25900
    [GIGAswitch] Polling for file transfer completion.
    [ERROR] FILE TRANSFER FAILED
    
    

        Did you start up the tftp server?
    
    MDL

    Michael,
    
    	Thanks for all the help and the pointers. Turned out the tftp
    server was started but pointing to /tmp area. The files I was trying
    to load was in the /usr/kits/HUBwatch. I moved everything to /tmp and
    everything worked fine.. 
    
    Thanks Again..
    
    John