| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
Hi folks, Not being a hubwatch person... Customer has a DECagent 90, bridge 90FL, and a 900 multiswitch, and hubwatch. The modules will be in the same 900MS. Can he integrate the DECagent 90 into hubwatch such that when he is managing (viewing) the 900MS, and notably the 90FL, that the DECagent seems to be seamlessly involved? That is, so that the customer can just click on the 90FL and get to that module? If so what changes have to be made thru HUBwatch? As well, can the DECagent still be used this way for other FL's in other 900MS's on the same segment (using the single DECagent 90)? -- thanx, Guy
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2275.1 | SLINK::HOOD | April showers bring vacation days | Mon May 15 1995 11:34 | 26 | |
(1) Create a single-slot community in the DECagent 90 for each DECbridge 90 to
be managed. Let's pretend you've called the communities Br1, Br2, etc.
(2) Using the HUBwatch Configuration->Add Module window, add the DECbridge 90
to each newly-created community. Be sure to correctly add the bridge's
MAC address!
(3) In your HUBwatch agents file, add an entry for each of the communities
you just created. The entries contain the following information:
IP Address: DECagent 90 address
Community: Br1 (next entry is Br2, etc)
MAC Address: MAC of the first bridge (next entry is mac of 2nd br,etc).
(4) Happily manage your bridge.
Background: The DECbridge 90 is an old device that does not speak SNMP. It
requires a DECagent 90 to translate between RBMS and SNMP. HUBwatch only
speaks SNMP. So, HUBwatch sends requests to the DECagent 90, which translates
them and sends them to the bridge. HUBwatch only gets the bridge's MAC
address from the DEChub 900. So, it uses its agents file to translate from
the bridge's MAC address to the DECagent 90's IP address (and in the process,
learns which DECagent 90 community includes the bridge).
Tom Hood
HUBwatch
| |||||
| 2275.2 | Cool! | CGOOA::BARNABE | Guy Barnabe - Digital Canada | Mon May 15 1995 12:08 | 4 |
Cool! Thanx very much! -- Guy | |||||