Conference netcad::hub_mgnt

    > (W) brouter: snmp timeout in summary_agroup
    
    This means SNMP timed-out.  
    
    Things to check:
    - Make sure the MAC/IP line in the Agents file for those brouters
      is correct.  (including the Community name).
    - Make sure the brouters have the correct rw Community and IP address,
      and that SNMP is enabled for the ethernet port.
    
    
    Tom Hood
    clearVISN

    Tom,
    
    I have checked (before I wrote this note) the MAC/IP line in the
    Agents file incl. the Community name and also the brouters have the
    correct rw Community and IP address and that SNMP is enabled for the
    ethernet port. Normal when you get a SNMP timeout you get a "No
    response from the agent" or not? Also with NETview this brouters are
    working (snmp get, getnext) what means the brouters have the  correct
    rw Community and IP address and SNMP is enabled for the ethernet port.
    (and are the same in the HUBwatch Agents file) 
    Is there any other reason possible why I get this error? 
    
    The HUB900,s where the brouters are installed are all connected
    via DECconcentrators in a FDDI ring. There are also problems with
    DECbridge900MX's and Risilience V1.0.3 in the same HUB900,s. 
    The problem is that Risilience V1.0.3 don't see the DECbridge900MX
    in the HUB900. HUBwatch works fine also for the DECbridge900MX what
    means that the agent file is ok. ( Risilience used the same agent file)
    Standalone Risilience is working with this DECbridge900MX! What I see
    in a trace is that the GET SYSobjectID won't answer. (community public
    is the only with works!) I have tryid to tested both problems in our
    test HUB (also via a concentrator and with the same hardware rev,s and
    firmware rev's) but I can't reproduce this situation. It is difficult
    to troubleshoot at the customer site because the HUB's are on the 
    Amsterdam Stock Exchange on the production network what means I only 
    may look to this HUB's or work after the Stock Exchange is closed.       
    
    I know this are 2 different problems but maybe the reason is the same?
    What is the best thing to do now? make 1 or 2 ipmt cases?
    
    Ronald
          

Random answers:

(1) DECbridge 900MX & agents file:
    When this is in a DEChub 900, and you are managing it as a part of
    the DEChub 900, the agents file is not used.  HUBwatch and Resilience
    both ask the DEChub 900 what modules are installed, and how to access
    those modules.

(2) DECbridge 900MX & Resilience:
    This is a supported module, and I've seen it work.  (The hub in my
    office contains a DECbridge 900MX.)  There is something broken in
    the bridge if it is not answering the GET for sysObjectId. 

By the way, Resilience 1.* uses a different scheme to get hub module
information than HUBwatch does.  In a future release of Recovery
Manager, this will be changed.

Tom Hood
clearVISN eng

    	Ronald,
    
    See note 2593 for some HUBwatch/DECbrouter90 Sysoid issues.... re: the
    base note, are all 15 brouters running 9.14, or are only the 5 failing
    brouters running 9.14, and the others running 10.x?
    
    		regards,
    
    -Chuck O.
     NPB Router Interop
    

    
    repl .3
    
    Tom, thanks for your answer, I have this also working in my office but 
    not on the customer site. 5 out of 5  module's give the same problem
    but the customer has also a lot DECswitch900EF's with no problems
    (same firmware). 
    
    repl .4
    
    Chuck, thanks for your answer. All the 15 brouters have 9.14. (I have
    not checked this but this is the info from the customer). I will check
    this again when? I go on-site.