| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1683.1 | How "similar" is it? | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Nov 11 1994 12:10 | 11 |
| Please give more information about the configuration; what's in the hub along
with the bridge, where is the DECagent 90 and what's in that hub (if it's in a
hub).
This problem can stem from many things (as was pointed out in the replies to
note 1506). Specific configuration details will help tremendously.
One other thing. Is it a DECbridge 90 or 90FL? What is the revision of the ROM
(listed in the first line of the banner just before the Ethernet address).
...Roger...
|
| 1683.2 | Deja-vu | PADNOM::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Mon Nov 14 1994 06:58 | 6 |
|
any change that's DS90L/L+ are involved in your configuration??
if my memory serves me, microcode fix on Decserver90l/l+ cured this kind
of problem.
Jean-Yves
|
| 1683.3 | Its a DECbridge 90FL | BRUMMY::WILLIAMSM | Born to grep | Mon Nov 14 1994 08:32 | 19 |
| The customers current configuration is a DECbridge90FL, 90C thinwire
90SP Fibrerepeater and a DECasgent90 all in the same 90 series
backplane. He has tried removing the 90C and 90SP without changing
the problem. The 90FL and the agent have both been swapped, and the
thing has been factory reset many times. The latest flash images were
copied by the customer "over the net," and installed by him. The
bridge image is 3.1 and the Agent is 2.1. I don't know the ROM code.
Hubwatch has never worked on this backplane, however this customer does
manage other hubwatch systems that do work.
He can make an NCP /physical connection no problem.
What is the simplest possible system that would allow the Hubwatch
software to run?
regards, Michael Williams.
|
| 1683.4 | DECagent 90 is the hub master | ROGER::GAUDET | Because the Earth is 2/3 water | Mon Nov 14 1994 09:52 | 13 |
| First, what is a DECrepeater 90SP? I've never heard of it.
Second, if you have a DECagent 90 in the same hub backplane as the DECbridge
90FL, then everything is working as expected. The DECagent 90 is the hub
manager, so the DECbridge 90FL cannot be (there can only be one hub master at a
time). The DECbridge 90FL cannot be managed directly through HUBwatch. It must
be managed *THROUGH* a DECagent 90, which means that you must specify the
DECagent's IP address in order to manage the hub. You will then be able to
manage the DECbridge 90FL along with the repeaters in the hub.
I think your customer is confused about how DECbridge 90's are managed.
...Roger...
|
| 1683.5 | Remove Decbridge90 and try again | PADNOM::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Mon Nov 14 1994 10:19 | 7 |
| >> First, what is a DECrepeater 90SP? I've never heard of it.
i think it's a typo for DECrepeater90FS
try to remove the Decbridge90FL , when V2.1.3 of Decagent90 you can manage
all modules without Decbridge90 in same Hub.
jean-yves
|
| 1683.6 | | COL01::LOPEZ | Arturo Lopez drinks K�lsch at Cologne | Tue Nov 15 1994 11:56 | 13 |
| Do I have to enter the bridge community on the console of the
DECagent.
I tried to enter a new community on the community table of HUBWATCH,
in order to manage a remote bridge(not in the same HUB90)
with a DECagent.
But it does not work.
Do I have to enter it in the DECagent first anf then in HUBWATCH ?
Arturo Lopez
Cologne Germany
|
| 1683.7 | What versions of HUBwatch and DECagent? | ROGER::GAUDET | Because the Earth is 2/3 water | Tue Nov 15 1994 12:16 | 15 |
| Arturo...
You cannot add a remote community to the DECagent via the console (assuming you
are running the latest V2.1.3 code). You must add it to the agent's community
table via the HUBwatch Community -> Manage Table pulldown.
What do you mean by "it does not work." Do you mean HUBwatch will not allow you
to add it, or the agent rejects it? What does the Show Community display (menu
item 13) at the agent console tell you? Does it show that the remote community
has been added? Remember that community names must be unique among communities
(that is, a community can have the same read-only and read-write community
strings, but that string must not be the same as that of another community being
managed by that agent).
...Roger...
|