| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2124.1 | Some ideas | ROGER::GAUDET | Because the Earth is 2/3 water | Tue Mar 21 1995 07:35 | 16 |
| Yes, as you discovered, you must add additional communities to a DECagent
running V2.0 and later by using HUBwatch.
Can you be more specific on how the hubs are connected? Is there a DECrepeater
90FA or 90FL in each DEChub 90 that is connected to the DECrepeater 900FL in the
DEChub 900, or are the bridges DECbridge 90FL's? What is the firmware version
in the bridges? V3.1 should be sufficient to manage the devices you described,
although there is a V3.9 available (see other notes for details).
As a wild guess, if you are not bringing the network in through the front panel
of the bridge, and the bridges are DECbridge 90's, you need to place a
T-connector with two terminators on the front panel ThinWire port (or a
thickwire terminator on the thickwire connection if that's selected via the
front panel switch).
...Roger...
|
| 2124.2 | HUBwatch management of remote brdg90 via DA90 | MSDOA::LOVE | Do it with DNA | Tue Mar 21 1995 19:27 | 26 |
| The configuration is:
Computer room - DEChub900 backbone with a DECrepeater900FP connected to five
DECbridge 90s. Each DECbridge 90 is in a DEChub90. Three of the DEChub90s are
doubled. All but one of the single hub90 are fully populated with DECrepeaters
and DECservers. The DEChub900 has two DECswitch900EFs joined together via an
internal FDDI ring using the A B ports. Each of the DECrepeater ports are
connected to an internal 900 LAN and bridged via the DECswitch900. Each node
of a three node VAX Cluster will also use a DECswitch900 port. The DECagent 90
is in slot 7 of the non fully populated DEChub90. Thus inorder for the
DECagent to communicate with a module on another HUB90 the message must pass to
its HUB90 backplane to the bridge90 through fiber to the DECrepeater900FP down
to a internal 900 LAN up to the DECswitch900 then backdown to another HUB900
LAN to another port on the DECrepeater900FP down fiber to the other DECbridge90
and finally to its backplane and the module.
The DECagent only autoconfigures the HUB90 in which it resides. He then
creates a community in HUBwatch and populates is manually. Everything works
fine except he can not manage the remote bridge90 via HUBwatch. He can manage
it via a VAX using NCP Connect. By fine I mean he can manage the remote
repeaters and servers in the remote HUB90 but not the bridge90 in that same
HUB. The bridge90 in the same HUB90 as the DECagent is managed by HUBwatch.
He has HUBwatch for windows version 3.1. It sure would help if he could
autoconfigure the remote HUB?
Norm
|
| 2124.3 | | SLINK::HOOD | This is my new personal name for Notes | Tue Mar 21 1995 19:43 | 7 |
| What happens when your customer double-clicks on the DECbridge 90's?
It is *supposed* to work.
Is RBMS protocol (the DECagent 90 converts SNMP to RBMS to talk to the
DECbridge 90) filtered anywhere on the network between the DECagent 90 and
the DECbridge 90?
|
| 2124.4 | FYI | ROGER::GAUDET | Because the Earth is 2/3 water | Wed Mar 22 1995 14:00 | 3 |
| The RBMS protocol type is 80-38.
...Roger...
|
| 2124.5 | Not my knowledge | MSDOA::LOVE | Do it with DNA | Wed Mar 22 1995 21:17 | 5 |
| He has not turned on any filtering, but I will have him check.
Thanks
Norm
|
| 2124.6 | Still have the problem! | MSDOA::LOVE | Do it with DNA | Thu Mar 23 1995 13:00 | 16 |
| There are no filters on the network anywhere. I think the problem is our
(his and mine) understanding of how to set up communities. We went into the
out of band port and set the DA90's IP address and community name, "public-a"
to make it different from the HUB900's "public". We then went into HUBwatch
and created the agent, agent-a. When we activate it we get a window showing
the HUB with the bridge in slot 8, the DA90 in slot 7, the DECserver90L+ in
slot 6, and a DECrepeater90T in slot 4. The MUXserver90 in slot 5 does not
show up, as expected. None of the other modules in remote DEChub90s show
up. We then create other communities and manually enter the modules which
are bridges, repeaters, and servers. We can manage from HUBwatch everything
but the bridges in the remote HUBs. The bridge in the local HUB, the hub
in which the DA90 resides, is managed by HUBWatch fine. What are we doing
wrong?
Norm
|