| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2067.1 | | NETCAD::GERHARDT | Out of Control | Thu Mar 02 1995 22:57 | 3 |
| each hub needs a bus Master, regardless of the rev of the DECagent.
if the hubs are filled with DECrepeater 90T and DECrepeater 90FA,
then there is no bus master in those hubs.
|
| 2067.2 | Can you replace the DECrepeater 90FA's with DECbridge 90FL's ? | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Mar 03 1995 11:12 | 20 |
| Keith is correct. The need for a bus master (or HUB master as the case may be)
is on a per-hub basis. The DECagent can manage the modules within the hub in
which it is installed without a DECbridge, but any "remote" hubs (that is, those
that do not contain the DECagent) must contain a hub master with which the
DECagent can communicate. The only remote hub master that the DECagent supports
is the DECbridge 90/90FL.
Given the configuration you described, you need two (2) DECagents in order to
remain within the 64 modules per agent specification (11 hubs x 8 modules/hub =
88 modules), assuming the hubs are all fully populated. In addition, you will
need ten (10) DECbridge 90 or 90FL modules. If I can make the assumption that
the hubs are interconnected via either the fiber or the AUI port of the
DECrepeater 90FA modules, you could replace the 90FA repeaters with DECbridge
90FL modules and realize the same connectivity. You will then need to configure
the hubs into the DECagents via an SNMP manager (e.g. HUBwatch) in whatever
combination you deem appropriate.
Hope this helps.
...Roger...
|
| 2067.3 | HUBwatch see all modules? | BOHIO::JRUIZ | If you can't convince'm... CONFUSE'M | Sun Mar 05 1995 19:00 | 5 |
| Thanks for the information. I'm using HUBwatch and if we replace the
DECrepeater 90FA with DECbrifge 90FL, how i can setup from HUBwatch?,
or HUBwatch would see all modules automactly?
Julio
|
| 2067.4 | Very easy to do | ROGER::GAUDET | Because the Earth is 2/3 water | Mon Mar 06 1995 12:09 | 18 |
| Julio...
Adding additional communities (hubs) to be managed by a DECagent is all clearly
documented in the HUBwatch documentation. By adding a new community to the
DECagent and then manually adding just the bridge to that community, the
DECagent will discover the repeaters in that community. Then you can see all
the modules in the hub from HUBwatch.
In brief, you bring up HUBwatch by specifying the IP address of the DECagent,
then go to the Community -> Manage Table window. From there you add new
communities (hubs) giving each a unique set of community strings (read-only and
read-write). After you "Make Current" the desired community (it will be empty),
you just add the bridge to its correct slot. Auto-discovery of the repeaters
will then take place. If you do not have HUBwatch polling enabled, you will
need to refresh the view to see the repeaters. Auto-discovery takes about 20
seconds or so.
...Roger...
|
| 2067.5 | Works fine... | BOHIO::JRUIZ | If you can't convince'm... CONFUSE'M | Mon Mar 06 1995 17:27 | 5 |
| Roger,
Thank for the information, works very good...
Julio
|