Conference netcad::hub_mgnt

You didn't mention where your DECagent 90 is.  In fact, you didn't say 
anything about your DECagent 90.  Without a DECagent 90, you cannot manage 
your DECbridge 90 with any rev of HUBwatch.

Assuming you *do* have a DECagent 90 on your LAN, you do the following:
	- Create a DECagent 90 community, and add your DECbridge 90 to it.
	- Create a HUBwatch agents file record with the MAC of the bridge,
	  and the IP address of the DECagent 90, with the community as the
	  name of the community you just created.

Nothing in this changed in any way for V4.0 of HUBwatch.

    
    
    OK.   Thanks Tom.   This is the first site where I plugged a Bridge 90
    into a HUB900.  Usually, the bigger hubs have the bigger bridges, and
    the smaller hubs have the 90's and the agents...
    
    Sorry to imply a differnt software rev, or a bug.   
    
    I DO have a DECagent 90 in some of the onsite Hub 90's, and I will add
    the Bridge 90 module to the agent table of my DECagent 90 module.
    
    thanks for the quick response.  You guys are wonderful.
    
    JR
    
    

    Hello.
    
    	I have another question.    I pulled up my DECagent 90's hub
    community under HUBwatch, and (along with it's 90-series hub entries) I
    added an entry for a fake community name (READ=read, READ/WRITE=write)
    for the DECbridge 90FL installed in one of my Hub900's.  There is only
    ONE DECagent on site (It's managing 3 16-slot communities), and now it
    includes an entry for my Bridge 90FL in the fake community, which I
    created as a "DEChub 900".   I can successfully click on the bottom MAKE
    CURRENT button of the DECagent's remote communities, and a partial
    representation of my HUB900 comes up.  I see only the DECbridge 90FL
    which I defined in slot #1.
    
    Tom's note in .-2 said:
    
  > Assuming you *do* have a DECagent 90 on your LAN, you do the following:
  >   - Create a DECagent 90 community, and add your DECbridge 90 to it.
  >   - Create a HUBwatch agents file record with the MAC of the bridge,
  >     and the IP address of the DECagent 90, with the community as the
  >     name of the community you just created.
    
    I performed the first step, but I am confused about how to perform the
    second function.  I tried to hand-edit my HW_AGENTS.DAT file, but I
    must have done something wrong.   I cannot bring up my HUB 900, using
    the HUB900's MAM IP entry, and click from the DECrepeater 900TM to the
    DECbridge 90FL under the same HUB 900 View.  (For what it's worth, the 
    entries that I hand-entered for some of DECserver 90TL modules in the 
    HUB90's don't work correctly either, so I must have done something wrong).
    
    I can click on the DECagent 90 (Under the MANAGE TABLE pull-down) entry
    and bring up that HUB90, and pull down the fake entry (for my bridge 90FL 
    in the HUB900), at the bottom of it's community table but that is not 
    very intuitive for my customer.
    
    Should I be using the fake community name ("read", or "write"), or
    should  I be using the REAL community name of the DECagent 90 that is
    managing the Bridge 90FL?  
    
    This is the entry that I think should work:, in C:\HUBWATCH\USERDATA\
    HW_AGENTS.DAT, but I have tried several other options:
    

132.100.3.1 agent90 "write" 5 2 08-00-2B-91-ED-4E BRIDGE #  My Bridge 90FL

    
	I won't be onsite again for a week or so.

JR
    
    
    
    

Your customer does not ever need to know about the alternate community
once things are properly configured.

I left out one step for the DECbridge 90's...

(1) Use the Configure-> Add menu to add the DECbridge 90 to the DEChub 900.
    ^
    |
    +----Sorry, I left this out...

(2) Create a DECagent 90 community...
(3) Add the record to the agents file (this does not need (and should not be)
    done by hand!  Use the Community->manage table window.)

When this is done, if you use HUBwatch to manage the DEChub 900, you will
see the DECbridge 90, and will be able to manage it directly.

Incidentally, this is all completely documented in the HUBwatch Installation
and Configuration manual.


Tom Hood
HUBwatch