Conference netcad::hub_mgnt

777.0. "Hubwatch T2.8 and Agent T2.0.10" by RDGENG::GREID (Bang that head that doesn't Bang !) Tue Mar 01 1994 04:56

    I have a couple of questions regarding T2.8 Hubwatch and T2.0.10
    Agent software.
    
    The upgrade to T2.8 was very simple and is working fine. I have just
    upgraded one of our DECAgent 90s to T2.0.10 and have installed it
    into a DECHUB with a DECBridge 90 running V3.1 and have a DECserver
    90M in Slot 1, a DECserver 90TL in Slot 2, and a DECserver 90L+ in
    slot three. 
    
    Question 1:
    
    	When I double click on the DECserver 90M I get a window pop up
    with the error "No Agent specified for the slot mac address - please
    check log messages in the Hubwatch startup window". Firstly, is this
    server supported yet as it was autodiscovered ok, or can I just not
    interogate it yet. Incidentally I had the same when the Agent was 
    running V1.1.
    
    Question 2:
    
    	The DECserver 90TL in slot 2 was not autodiscovered, but when 
    I try to add it, I can't select OK or APPLY, I have left the READ-ONLY 
    and READ-WRITE strings to public so is this not supported yet. I have
    added the DECserver 90L+ ok.
    
    Question 3:
    
    	Why has the format of the DECAgent 90 console been changed from the
    	way it was in V1.1 (please note that I havent upgraded any of our
    	agents from V1.1 until now) ? What was wrong with the format
    	before. IMO this doesn't look as professional and scrolls up and
        off the screen, this is on obervation, so please don't burn me for
        this, I am just interested.
    
    Question 4:
    
    	With the T2.0.10 I see no option to add a module, does this mean
    that all modules are autodiscovered now (excuse me If on first look I
    have missed something).
    
    
    Thanks for your time,
    
    Giles
    REO Networks Support.
    

    Both 1&2:
         The DECserver90M & TL do not support management via the hub
    management channel; at most (depending on rev level) they tell the hub
    thier address, which the hub agent (either DENMA or the 900 agent)
    passes on to HUBwatch.  HUBwatch must have an entry in the agents file
    in order to match this address information and get the community needed
    to manage the device.