Conference netcad::hub_mgnt

    Hi!
    
      It seems like you did some homework, but didn't do the main part
    (which would have saved you the homework)...8-) !!!
    
      Couldn't you install HUBwatch (I think V4.1 is out for UNIX)
    properly?
    
      Cheers,
    
      Pedro
    

    HUBloader is only guaranteed to work with modules in the DEChub
    Consolidated kit - and for good reason.  The way HUBloader works
    is that it does a series of SNMP Sets to a device to get it into 
    the state where the device requests a TFTP Load.  The MIB objects
    that are set are device dependent.  Thus, information in the
    Consolidated kit identify the devices in the kit and what MIB
    objects need to be set.  Note it is actually a TFTP server that 
    does the actual loading - not HUBloader.
    
    Router code for the DECswitches are not part of the kit and cannot
    be put into a TFTP load request mode through SNMP.  This must be done
    through the CLI interface on the routers.
    
    
    							John

        re: .0:

        In a routing class we offer, we have done a operation
        similar to what you are trying to accomplish.
        DEChub 900 MS with a DECswitch 900EE in the one of the slots
        - we set an IP address in the module
        - using HUBwatch V4.1.2  for Windows along with HUBLOAD & the TFTP
                server:
                        start TFTP server
                        use HUBLOAD to install the routing .BIN file into
                           the switch (actually the TFTP server does the
                           loading)
        - works fine -- we just stuff the routing BIN file in the directory
                along with all the other firmware files.
        
        Although I'm not a HUB/HUBload specicialist I believe it works because
        HUBLOAD tells the module (via SNMP sets I assume) to request
        a TFTP load. And the module is still running the switch firmware
        which understands HUBLOAD's "commands".

        However should you choose to go the other way, be aware that it won't 
        work the same way. Once the routing image is loaded, it won't
        respond to HUBLOAD's commands -- in fact it does not support
        SNMP sets. So to go from the routing image to the level 2 
        switching image, you'll need to use the router console to 
        accomplish this:
                * TALK 6
                Config> BOOT
                Boot config> LOAD REMOTE
                  and then answer the questions about where your
                  TFTP server is, and the file to load (use the
                  level 2 switching firmware file (eg DEMBP111.BIN
                  in the case of the DECswitch 900EE)

        Hope this helps
        
        Michael

    huh?
    
    .1	- I've installed HUBWATCH V4.0, the only version we were selling
    customers at the time... ~ 3 mos ago.  There is no option or subset to
    install HUBLOAD.  There's only 1 option, which I took...
    >>> install hubwatch correctly...
    Unless I'm mistaken, # setld -l 'product_name' is the correct way to
    install subsets on d-Unix????
    
    .2  - I don't think I understand your reply, and I'll send you mail
    offline... are you telling me that I shouldn't be able to make the
    900EF a router?
    
    .3  - Thanks for the info... unfortunately, I'm not sure what you've
    instructed me to do...  if you care to elaborate, please send Email,
    	
    SCASS1::GALVIN
    
    thanks,
    
    /Mic
    

    .3
    
    Michael, in our reply, you indicate that you copied the .bin file(s) to
    the proper directory and that the TFTP Server worked fine... How did
    you setup the TFTP Server?
    
    I have given the 900EF an IP address.  When I "plug" it into the
    DEChub900 I can see it just fine when I bring up HUBWATCH, however, I
    can't doing anything other than monitor it... I can't change anything.
    Also, it thinks it's a bridge, so it's not hubloading the routing file.
    
    In talking to another guy in this conference, he said there's another
    kit that contains additional ENVIRONMENT variables...?  Also, if that's
    true (remember, I'm running V4.0), have these variables been propagated
    to the V4.1 kit?
    
    Again, I'm running d-Unix V3.2C...
    
    thanks,
    
    /Mic
    
    

    there is a routing conference
    
    IROCZ::USER4:[NOTES$LIBRARY]COMMON_BROUTERS.NOTE;1